-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#3696 - tc39-test262 Crate #3708
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3708 +/- ##
==========================================
+ Coverage 47.24% 47.37% +0.12%
==========================================
Files 476 461 -15
Lines 46892 44846 -2046
==========================================
- Hits 22154 21245 -909
+ Misses 24738 23601 -1137 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge comments
@@ -220,54 +220,6 @@ impl RunTest<OptimizerOptions, TestResult> for Test { | |||
} | |||
} | |||
|
|||
/// Creates the test result from the outcome and message. | |||
fn create_result<S: Into<Box<str>>>( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to helper function (Out of Trait)
@@ -87,9 +93,13 @@ static FEATURE_EDITION: phf::Map<&'static str, SpecEdition> = phf::phf_map! { | |||
// https://github.com/tc39/proposal-set-methods | |||
"set-methods" => SpecEdition::ESNext, | |||
|
|||
// Regular Expression Pattern Modifiers | |||
// https://github.com/tc39/proposal-regexp-modifiers | |||
"regexp-modifiers" => SpecEdition::ESNext, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicate in line 76
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for all the work!
It's been several days going back and forth on this PR about whether to put the feature to editions map into the new crate or the tester.
On the one hand, features are part of the test262 suite and we may include them to also get the edition of a test. On the other hand, if we include them, we would need to keep the crate pretty much updated with every new commit to the test262 repo, which would be a pretty big maintenance work for us.
I'm tending towards leaving the editions on the tester, since I don't see many use cases for it aside from engine tests. What do you think?
I wonder if would be ok for tests that contains unknown features set edition to ESNext as a fallback option. I guess in that case they could be marked as ignored as well. Thinking long term:
|
That would also be a good option for the short-term. On the long term, I'm trying to push for adding this metadata to |
This Pull Request closes #3696.
It changes the following:
boa_tester
parser logic totools/tc39-test262
crate