Skip to content
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

Normative: Adds change-array-by-copy #2997

Merged
merged 1 commit into from
Mar 12, 2023
Merged

Conversation

acutmore
Copy link
Contributor

@ljharb ljharb added normative change Affects behavior required to correctly evaluate some ECMAScript source text pending stage 4 This proposal has not yet achieved stage 4, but may otherwise be ready to merge. has test262 tests proposal This is related to a specific proposal, and will be closed/merged when the proposal reaches stage 4. labels Jan 19, 2023
@ljharb ljharb requested review from syg, michaelficarra, bakkot and a team January 19, 2023 19:36
@jmdyck
Copy link
Collaborator

jmdyck commented Jan 19, 2023

Rather than leaving 'suggested change' comments here, I've submitted a PR against this PR's branch: acutmore#2

spec.html Outdated Show resolved Hide resolved
spec.html Show resolved Hide resolved
spec.html Outdated Show resolved Hide resolved
spec.html Outdated Show resolved Hide resolved
Copy link
Contributor

@syg syg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

spec.html Show resolved Hide resolved
spec.html Show resolved Hide resolved
spec.html Outdated Show resolved Hide resolved
spec.html Outdated Show resolved Hide resolved
@acutmore
Copy link
Contributor Author

acutmore commented Feb 6, 2023

This proposal is now Stage 4: tc39/proposals@ad4df84
Commits squashed and rebased.

@acutmore acutmore marked this pull request as ready for review February 6, 2023 10:34
@acutmore acutmore changed the title [Stage 4 Draft] Normative: Adds change-array-by-copy [Stage 4] Normative: Adds change-array-by-copy Feb 6, 2023
@ljharb ljharb added has stage 4 This PR represents a proposal that has achieved stage 4, and is ready to merge. and removed pending stage 4 This proposal has not yet achieved stage 4, but may otherwise be ready to merge. labels Feb 6, 2023
Copy link
Contributor

@bakkot bakkot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM other than typo.

spec.html Show resolved Hide resolved
@ljharb ljharb force-pushed the change-array-by-copy branch from 5a1df73 to 269c803 Compare February 26, 2023 04:45
Copy link
Member

@michaelficarra michaelficarra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. There are some opportunities I noticed to use our new interval notation, but I'm not sure what our editorial stance is on that at the moment, so this is fine as-is.

@michaelficarra michaelficarra added the editor call to be discussed in the next editor call label Mar 2, 2023
spec.html Outdated Show resolved Hide resolved
@syg syg added the ready to merge Editors believe this PR needs no further reviews, and is ready to land. label Mar 8, 2023
spec.html Show resolved Hide resolved
spec.html Show resolved Hide resolved
Co-authored-by: Ashley Claymore <[email protected]>
Co-authored-by: Nicolò Ribaudo <[email protected]>
Co-authored-by: Robin Ricard <[email protected]>
Co-authored-by: Michael Dyck <[email protected]>
Co-authored-by: Shu-yu Guo <[email protected]>
Co-authored-by: Jordan Harband <[email protected]>
Co-authored-by: Linus Groh <[email protected]>
@ljharb ljharb force-pushed the change-array-by-copy branch from 82a40c9 to 4a32716 Compare March 11, 2023 22:17
@ljharb ljharb changed the title [Stage 4] Normative: Adds change-array-by-copy Normative: Adds change-array-by-copy Mar 12, 2023
@ljharb ljharb merged commit 4a32716 into tc39:main Mar 12, 2023
jmdyck added a commit to jmdyck/ecma262 that referenced this pull request Mar 18, 2023
During review of PR tc39#2997, @michaelficarra suggested changing:
> the intrinsic object listed in column one of {Table 68} for _exemplar_.[[TypedArrayName]]
to:
> the intrinsic object associated with the constructor name _exemplar_.[[TypedArrayName]] in {Table 68}
in the new AO TypedArrayCreateSameType.
(tc39#2997 (review))

This commit makes the same change in the pre-existing AO TypedArraySpeciesCreate.
@ljharb ljharb removed the editor call to be discussed in the next editor call label Mar 21, 2023
ljharb pushed a commit to jmdyck/ecma262 that referenced this pull request Mar 21, 2023
During review of PR tc39#2997, @michaelficarra suggested changing:
> the intrinsic object listed in column one of {Table 68} for _exemplar_.[[TypedArrayName]]
to:
> the intrinsic object associated with the constructor name _exemplar_.[[TypedArrayName]] in {Table 68}
in the new AO TypedArrayCreateSameType.
(tc39#2997 (review))

This commit makes the same change in the pre-existing AO TypedArraySpeciesCreate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has stage 4 This PR represents a proposal that has achieved stage 4, and is ready to merge. has test262 tests normative change Affects behavior required to correctly evaluate some ECMAScript source text proposal This is related to a specific proposal, and will be closed/merged when the proposal reaches stage 4. ready to merge Editors believe this PR needs no further reviews, and is ready to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants