github
/
boa
mirror of https://github.com/boa-dev/boa.git
1
0
Fork 0
Code Issues Releases Wiki Activity
Rust编写的JavaScript引擎，该项目是一个试验性质的项目。
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2264 Commits
22 Branches
24 Tags
683 MiB
Tree: 1965492f7c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1965492f7c'
${ noResults }
boa/boa_ast/Cargo.toml

25 lines
797 B
Raw Normal View History Unescape

Extract the ast to a crate (#2402) This should hopefully improve our compilation times, both from a clean build and from an incremental compilation snapshot. Next would be the parser, but it imports `Context`, so it'll require a bit more work. The number of file changes is obviously big, but almost nothing was changed, I just moved everything to another crate and readjusted the imports of the `parser` module. (Though, I did have to change some details, because there were some functions on the ast that returned `ParseError`s, and the tests had to be moved to the parser)
2 years ago
[package]
name = "boa_ast"
description = "Abstract Syntax Tree definition for the Boa JavaScript engine."
keywords = ["javascript", "js", "syntax", "ast"]
categories = ["parser-implementations", "compilers"]
version.workspace = true
edition.workspace = true
authors.workspace = true
license.workspace = true
repository.workspace = true
rust-version.workspace = true
[features]
Bump bitflags to 2.0.0 (#2666) Updated `bitflags`, overrides #2665.
2 years ago
serde = ["dep:serde", "boa_interner/serde", "bitflags/serde"]
First batch of `no_std` support for some sub-crates (#2544) <!--- Thank you for contributing to Boa! Please fill out the template below, and remove or add any information as you feel necessary. ---> This Pull Request enables support for `no_std` targets on some of our sub-crates. I intentionally left out `boa_ast` and `boa_cli` because they're the largest crates we have after `boa_engine`. `boa_gc` is a monster on its own, because we'll need to design a `no_std` multithreaded GC. Anyways, this changes the following: - Adds support for `no_std` on `boa_unicode`. - Adds support for `no_std` on `boa_profiler`. - Adds support for `no_std` on `boa_interner`. - Adds support for `no_std` on `boa_icu_provider`.
2 years ago
arbitrary = ["dep:arbitrary", "boa_interner/arbitrary", "num-bigint/arbitrary"]
Parser Idempotency Fuzzer (#2400) This Pull Request offers a fuzzer which is capable of detecting faults in the parser and interner. It does so by ensuring that the parsed AST remains the same between a parsed source and the result of parsing the `to_interned_string` result of the first parsed source. It changes the following: - Adds a fuzzer for the parser and interner. Any issues I raise in association with this fuzzer will link back to this fuzzer. You may run the fuzzer using the following commands: ```bash $ cd boa_engine $ cargo +nightly fuzz run -s none parser-idempotency ``` Co-authored-by: Addison Crump <addison.crump@cispa.de>
2 years ago
Extract the ast to a crate (#2402) This should hopefully improve our compilation times, both from a clean build and from an incremental compilation snapshot. Next would be the parser, but it imports `Context`, so it'll require a bit more work. The number of file changes is obviously big, but almost nothing was changed, I just moved everything to another crate and readjusted the imports of the `parser` module. (Though, I did have to change some details, because there were some functions on the ast that returned `ParseError`s, and the tests had to be moved to the parser)
2 years ago
[dependencies]
boa_interner.workspace = true
boa_macros.workspace = true
rustc-hash = "1.1.0"
Bump bitflags from 2.1.0 to 2.2.1 (#2868) Bumps [bitflags](https://github.com/bitflags/bitflags) from 2.1.0 to 2.2.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bitflags/bitflags/releases">bitflags's releases</a>.</em></p> <blockquote> <h2>2.2.1</h2> <h2>What's Changed</h2> <ul> <li>Refactor attribute filtering to apply per-flag by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/345">bitflags/bitflags#345</a></li> <li>Prepare for 2.2.1 release by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/346">bitflags/bitflags#346</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/bitflags/bitflags/compare/2.2.0...2.2.1">https://github.com/bitflags/bitflags/compare/2.2.0...2.2.1</a></p> <h2>2.2.0 (yanked)</h2> <h2>What's Changed</h2> <ul> <li>Create SECURITY.md by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/338">bitflags/bitflags#338</a></li> <li>add docs to describe the behavior of multi-bit flags by <a href="https://github.com/nicholasbishop"><code>@​nicholasbishop</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/340">bitflags/bitflags#340</a></li> <li>Add support for bytemuck by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/336">bitflags/bitflags#336</a></li> <li>Add a top-level macro for filtering attributes by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/341">bitflags/bitflags#341</a></li> <li>Prepare for 2.2.0 release by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/342">bitflags/bitflags#342</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/nicholasbishop"><code>@​nicholasbishop</code></a> made their first contribution in <a href="https://redirect.github.com/bitflags/bitflags/pull/340">bitflags/bitflags#340</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/bitflags/bitflags/compare/2.1.0...2.2.0">https://github.com/bitflags/bitflags/compare/2.1.0...2.2.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/bitflags/bitflags/blob/main/CHANGELOG.md">bitflags's changelog</a>.</em></p> <blockquote> <h1>2.2.1</h1> <h2>What's Changed</h2> <ul> <li>Refactor attribute filtering to apply per-flag by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/345">bitflags/bitflags#345</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/bitflags/bitflags/compare/2.2.0...2.2.1">https://github.com/bitflags/bitflags/compare/2.2.0...2.2.1</a></p> <h1>2.2.0</h1> <h2>What's Changed</h2> <ul> <li>Create SECURITY.md by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/338">bitflags/bitflags#338</a></li> <li>add docs to describe the behavior of multi-bit flags by <a href="https://github.com/nicholasbishop"><code>@​nicholasbishop</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/340">bitflags/bitflags#340</a></li> <li>Add support for bytemuck by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/336">bitflags/bitflags#336</a></li> <li>Add a top-level macro for filtering attributes by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://redirect.github.com/bitflags/bitflags/pull/341">bitflags/bitflags#341</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/nicholasbishop"><code>@​nicholasbishop</code></a> made their first contribution in <a href="https://redirect.github.com/bitflags/bitflags/pull/340">bitflags/bitflags#340</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/bitflags/bitflags/compare/2.1.0...2.2.0">https://github.com/bitflags/bitflags/compare/2.1.0...2.2.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bitflags/bitflags/commit/0c318c0d77ed63ad4ee9bfdf1d2c486993b18b37"><code>0c318c0</code></a> Merge pull request <a href="https://redirect.github.com/bitflags/bitflags/issues/346">#346</a> from KodrAus/cargo/2.2.1</li> <li><a href="https://github.com/bitflags/bitflags/commit/a51c0532865ccd26de1a55d212ba90304199c463"><code>a51c053</code></a> prepare for 2.2.1 release</li> <li><a href="https://github.com/bitflags/bitflags/commit/638707f0f0a38499dbc4cfdd7ef10d8106647309"><code>638707f</code></a> Merge pull request <a href="https://redirect.github.com/bitflags/bitflags/issues/345">#345</a> from KodrAus/fix/recursion</li> <li><a href="https://github.com/bitflags/bitflags/commit/f3f3b6a7b00f79e05601afe07fe806d36fddd846"><code>f3f3b6a</code></a> add docs to example generated flags</li> <li><a href="https://github.com/bitflags/bitflags/commit/588d13298ea5ba0ab37c57c947e0a47fe5335c8a"><code>588d132</code></a> refactor attribute filtering to apply per-flag</li> <li><a href="https://github.com/bitflags/bitflags/commit/cbcafa710fc31172511e62efa06ad9eb214e4734"><code>cbcafa7</code></a> Merge pull request <a href="https://redirect.github.com/bitflags/bitflags/issues/342">#342</a> from KodrAus/cargo/2.2.0</li> <li><a href="https://github.com/bitflags/bitflags/commit/61df53a791cfdd681bc4adcea12796c0bdef1ca5"><code>61df53a</code></a> prepare for 2.2.0 release</li> <li><a href="https://github.com/bitflags/bitflags/commit/780f456840a2c2755b574397b3297e213a1e8b9f"><code>780f456</code></a> Merge pull request <a href="https://redirect.github.com/bitflags/bitflags/issues/341">#341</a> from KodrAus/fix/doc-alias</li> <li><a href="https://github.com/bitflags/bitflags/commit/405e7de8ee8d9fea1ecf67a7bd234a9bcf45c3b9"><code>405e7de</code></a> updates macro field names</li> <li><a href="https://github.com/bitflags/bitflags/commit/561fe509b081b2bf4d71a279389a03b9c3207b01"><code>561fe50</code></a> add a top-level macro for filtering attributes</li> <li>Additional commits viewable in <a href="https://github.com/bitflags/bitflags/compare/2.1.0...2.2.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bitflags&package-manager=cargo&previous-version=2.1.0&new-version=2.2.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
1 year ago
bitflags = "2.2.1"
Extract the ast to a crate (#2402) This should hopefully improve our compilation times, both from a clean build and from an incremental compilation snapshot. Next would be the parser, but it imports `Context`, so it'll require a bit more work. The number of file changes is obviously big, but almost nothing was changed, I just moved everything to another crate and readjusted the imports of the `parser` module. (Though, I did have to change some details, because there were some functions on the ast that returned `ParseError`s, and the tests had to be moved to the parser)
2 years ago
num-bigint = "0.4.3"
Bump serde from 1.0.159 to 1.0.160 (#2807) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.159 to 1.0.160. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/serde/releases">serde's releases</a>.</em></p> <blockquote> <h2>v1.0.160</h2> <ul> <li>Make derived serializer/deserializer internals <code>doc(hidden)</code> (<a href="https://redirect.github.com/serde-rs/serde/issues/2426">#2426</a>, thanks <a href="https://github.com/compiler-errors"><code>@​compiler-errors</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/serde/commit/0c6a2bbf794abe966a4763f5b7ff23acb535eb7f"><code>0c6a2bb</code></a> Release 1.0.160</li> <li><a href="https://github.com/serde-rs/serde/commit/a80d830f274876a6d59fdc3c17e064b065231772"><code>a80d830</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/serde/issues/2426">#2426</a> from compiler-errors/dont-doc-private</li> <li><a href="https://github.com/serde-rs/serde/commit/5f3fd9994e058cf1251a056d86b45a8a99f86be4"><code>5f3fd99</code></a> Make serializer/deserializer internals doc(hidden)</li> <li>See full diff in <a href="https://github.com/serde-rs/serde/compare/v1.0.159...v1.0.160">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde&package-manager=cargo&previous-version=1.0.159&new-version=1.0.160)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
1 year ago
serde = { version = "1.0.160", features = ["derive"], optional = true }
First batch of `no_std` support for some sub-crates (#2544) <!--- Thank you for contributing to Boa! Please fill out the template below, and remove or add any information as you feel necessary. ---> This Pull Request enables support for `no_std` targets on some of our sub-crates. I intentionally left out `boa_ast` and `boa_cli` because they're the largest crates we have after `boa_engine`. `boa_gc` is a monster on its own, because we'll need to design a `no_std` multithreaded GC. Anyways, this changes the following: - Adds support for `no_std` on `boa_unicode`. - Adds support for `no_std` on `boa_profiler`. - Adds support for `no_std` on `boa_interner`. - Adds support for `no_std` on `boa_icu_provider`.
2 years ago
arbitrary = { version = "1", features = ["derive"], optional = true }