mirror of https://github.com/oxc-project/oxc.git synced 2026-09-14 19:36:11 +08:00

Files

T

History

碳苯 Carbon bfb4c57a5d feat(parser): distinguish unapplied no-side-effects comments (#26120 )

## Summary 

Fixes #26088

`NO_SIDE_EFFECTS` can either be applied to a function:

```rs
/* #__NO_SIDE_EFFECTS__ */ function foo() {}
```

Or be meaningless for its position, since it only works on function
declaration:
```rs
/* #__NO_SIDE_EFFECTS__ */ value;
```

But oxc could not distinguish these two cases. 

This PR adds `CommentContent::NoSideEffectsNotApplied`, mirroring the
existing `PureNotApplied`.

---------

Co-authored-by: Cameron <cameron.clark@hey.com>

2026-09-03 11:14:24 +01:00

src

feat(parser): distinguish unapplied no-side-effects comments (#26120 )

2026-09-03 11:14:24 +01:00

Cargo.toml

release(crates): oxc v0.148.0 (#26198 )

2026-09-01 08:15:07 +00:00

CHANGELOG.md

release(crates): oxc v0.148.0 (#26198 )

2026-09-01 08:15:07 +00:00

README.md

…

README.md

Oxc AST

Abstract Syntax Tree definitions for JavaScript, TypeScript, and JSX.

Overview

This crate provides comprehensive AST (Abstract Syntax Tree) node definitions that support the full spectrum of JavaScript and TypeScript syntax, including JSX. The AST closely follows ECMAScript specifications while providing ergonomic APIs for manipulation.

Key Features

Complete language support: JavaScript, TypeScript, JSX, and TSX
ECMAScript compliant: AST structure follows official specifications
Memory efficient: Designed to work with oxc_allocator for fast allocation
Visitor patterns: Integrates with oxc_ast_visit for traversal
Type-safe: Leverages Rust's type system for correctness

AST Design Principles

The AST design differs from estree in several important ways:

Explicit identifiers: Uses specific types like BindingIdentifier, IdentifierReference, and IdentifierName instead of generic Identifier
Precise assignment targets: AssignmentExpression.left uses AssignmentTarget instead of generic Pattern
Literal specialization: Replaces generic Literal with BooleanLiteral, NumericLiteral, StringLiteral, etc.
Evaluation order: Field order follows ECMAScript evaluation order for consistency

Architecture

The AST is designed for:

Parse: Efficient construction during parsing
Transform: Easy manipulation during transpilation
Visit: Systematic traversal for analysis
Codegen: Clean conversion back to source code

All AST nodes are allocated in an arena (oxc_allocator) for optimal performance.