v0.11 #6
Merged
v0.11 #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RageKnify
approved these changes
Jan 12, 2021
_posts/2021-01-10-boa-release-11.md
Outdated
|
|
||
| ## Test 262 | ||
|
|
||
| Test262 is the implementation conformance test suite maintained by TC39. It's used by nearly all engines to measure how conformant they are to the specification. Boa pulls the tests in-tree and runs against PRs and on a nightly basis. Test262 doesn't sit still, so since the last release we've updated our reference to make sure we're running against the latest spec. You can find more about Test262 [here](https://github.com/tc39/test262). |
There was a problem hiding this comment.
I don't think the term nightly fits here, what do you think?
Suggested change
| Test262 is the implementation conformance test suite maintained by TC39. It's used by nearly all engines to measure how conformant they are to the specification. Boa pulls the tests in-tree and runs against PRs and on a nightly basis. Test262 doesn't sit still, so since the last release we've updated our reference to make sure we're running against the latest spec. You can find more about Test262 [here](https://github.com/tc39/test262). | |
| Test262 is the implementation conformance test suite maintained by TC39. It's used by nearly all engines to measure how conformant they are to the specification. Boa pulls the tests in-tree and runs them against all PRs. Test262 doesn't sit still, so since the last release we've updated our reference to make sure we're running against the latest spec. You can find more about Test262 [here](https://github.com/tc39/test262). |
Razican
reviewed
Jan 12, 2021
_posts/2021-01-10-boa-release-11.md
Outdated
Comment on lines
42
to
50
| ## Embedding examples | ||
|
|
||
| We are still working on what the public API should look like, some of these decisions are driven by feedback and the constant changing way which Boa works. | ||
| Not only you can run Boa against javascript today you can also embed your own objects and classes into the engine before it's ran. | ||
|
|
||
| We've offered an [example](https://github.com/boa-dev/boa/blob/master/boa/examples/classes.rs) to show how a class can be constructed in Rust then added to the environment before executing your scripts. | ||
| This should offer a great insight into how you can interop Rust with JavaScript by using Boa. | ||
|
|
||
| If there are any examples you would like added, please raise an issue on the main repository. |
There was a problem hiding this comment.
We are missing some examples until boa-dev/boa#634 (or an equivalent PR) get merged. Should we add some code examples here? Or at least mention that using a Context we can register global functions, global classes and so on.
We could mention the Context::register_global_function(), Context::register_global_class() and Context::register_global_property() functions, to make our users understand how to extend Boa.
There was a problem hiding this comment.
Yeah I like the sound of that
_posts/2021-01-10-boa-release-11.md
Outdated
|
|
||
| Test262 is the implementation conformance test suite maintained by TC39. It's used by nearly all engines to measure how conformant they are to the specification. Boa pulls the tests in-tree and runs against PRs and on a nightly basis. Test262 doesn't sit still, so since the last release we've updated our reference to make sure we're running against the latest spec. You can find more about Test262 [here](https://github.com/tc39/test262). | ||
|
|
||
| Since v0.10 we have almost doubled on spec conformance, and reduced panics from hundreds to less than 50. A year ago Boa didn't even track itself against Test262 so it was difficult to know how compliant we were to the spec, today not only do we track all changes against Test262 but we can see progress on a PR to PR basis. |
There was a problem hiding this comment.
Suggested change
| Since v0.10 we have almost doubled on spec conformance, and reduced panics from hundreds to less than 50. A year ago Boa didn't even track itself against Test262 so it was difficult to know how compliant we were to the spec, today not only do we track all changes against Test262 but we can see progress on a PR to PR basis. | |
| Since v0.10 we have almost doubled on spec conformance, and reduced panics from hundreds to 25 (tracked in [#817](https://github.com/boa-dev/boa/issues/817)). A year ago Boa didn't even track itself against Test262 so it was difficult to know how compliant we were to the spec, today not only do we track all changes against Test262 but we can see progress on a PR to PR basis. |
_posts/2021-01-10-boa-release-11.md
Outdated
Comment on lines
64
to
66
| ## Thank You | ||
|
|
||
| Everything in this release has been such a huge effort, we thank everyone who contributed, whether it was features, fixes or raising bugs. |
There was a problem hiding this comment.
Here I would mention the contributors since the last release. Especially for the ones outside of the org, and the new memberships in the organization.
I would also add links to the good first issues and maybe also issues where help is wanted, so that potential contributors know where to start.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.