Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upLet's remove the IsDetachedBuffer check in 22.2.4.3, step 18.a #1002
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@anba want to whip up a needs-consensus PR? |
added a commit
to anba/ecma262
that referenced
this issue
Sep 22, 2017
anba
referenced this issue
Sep 22, 2017
Merged
Normative: Remove detached array buffer check prior to calling CloneArrayBuffer #1009
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This test is valid both in the current spec and after your PR, right? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
anba
Sep 25, 2017
Contributor
This test is valid both in the current spec and after your PR, right?
No. After the update "get prototype" will also be printed for the test(Int32Array, Int32Array) call.
No. After the update "get prototype" will also be printed for the |
added a commit
to anba/ecma262
that referenced
this issue
Jul 18, 2018
ljharb
closed this
in
#1009
Jul 18, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
anba commentedSep 16, 2017
I didn't remove the step in #844 to avoid normative changes in that PR, but since this check is only implemented correctly in SpiderMonkey and CloneArrayBuffer will again check for detached buffers, it doesn't seem terrible useful to me to test for detached buffers in this step.
Test case for the current spec.