-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
[Merged by Bors] - Implement Array.from #1831
Conversation
d64f00d
to
7dbab31
Compare
Codecov Report
@@ Coverage Diff @@
## main #1831 +/- ##
==========================================
- Coverage 45.98% 45.86% -0.12%
==========================================
Files 206 206
Lines 17057 17097 +40
==========================================
- Hits 7844 7842 -2
- Misses 9213 9255 +42
Continue to review full report at Codecov.
|
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 the contribution! I have some suggestions to improve the code, if you don't mind :)
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.
Just got one tiny change, otherwise looks great!
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.
It looks pretty good! Thank you for the contribution :)
I added some comments, feel free to give them a look, but it's pretty good from my side!
@nrabulinski please, check the comments and see if you can fix what was mentioned, and re-base the branch, so that we can merge this as soon as possible :) |
VM implementation
Fixed tests (84):
Broken tests (2):
|
@nrabulinski it would be nice to get this merged during the weekend, for the 0.14 release of Boa. Do you have time to check the comments by @jedel1043? |
- Make `IfAbruptCloseIterator` a pub(crate) macro since it's used in more places in the spec.
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.
The comments have been resolved :)
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.
No more nitpicks :)
bors r+ |
<!--- Thank you for contributing to Boa! Please fill out the template below, and remove or add any information as you feel neccesary. ---> This Pull Request fixes/closes #1784. There're still a few tests failing, notably: - `iter-set-elem-prop-non-writable` - we don't have generator functions implemented - `calling-from-valid-1-noStrict`, `iter-map-fn-this-non-strict` - `thisArg` in non-strict mode, when undefined, should be inherited (that's what I'm guessing, I haven't confirmed this, but strict counterparts do pass with `thisArg` being `undefined`) - `source-array-boundary`, `elements-deleted-after` - ~~Not sure yet, still investigating, but they also include thisArg, so perhaps function calling has an underlying issue?~~ Failing because `this` on the top level evaluates to an empty object instead of containing everything from the top scope Co-authored-by: HalidOdat <halidodat@gmail.com>
Pull request successfully merged into main. Build succeeded: |
<!--- Thank you for contributing to Boa! Please fill out the template below, and remove or add any information as you feel neccesary. ---> This Pull Request fixes/closes #1784. There're still a few tests failing, notably: - `iter-set-elem-prop-non-writable` - we don't have generator functions implemented - `calling-from-valid-1-noStrict`, `iter-map-fn-this-non-strict` - `thisArg` in non-strict mode, when undefined, should be inherited (that's what I'm guessing, I haven't confirmed this, but strict counterparts do pass with `thisArg` being `undefined`) - `source-array-boundary`, `elements-deleted-after` - ~~Not sure yet, still investigating, but they also include thisArg, so perhaps function calling has an underlying issue?~~ Failing because `this` on the top level evaluates to an empty object instead of containing everything from the top scope Co-authored-by: HalidOdat <halidodat@gmail.com>
This Pull Request fixes/closes #1784.
There're still a few tests failing, notably:
iter-set-elem-prop-non-writable
- we don't have generator functions implementedcalling-from-valid-1-noStrict
,iter-map-fn-this-non-strict
-thisArg
in non-strict mode, when undefined, should be inherited (that's what I'm guessing, I haven't confirmed this, but strict counterparts do pass withthisArg
beingundefined
)source-array-boundary
,elements-deleted-after
-Not sure yet, still investigating, but they also include thisArg, so perhaps function calling has an underlying issue?Failing becausethis
on the top level evaluates to an empty object instead of containing everything from the top scope