Editorial: Describe Stack Frames using Records#37
Draft
Editorial: Describe Stack Frames using Records#37
Conversation
This was referenced Feb 17, 2021
ljharb
requested changes
Feb 17, 2021
Member
ljharb
left a comment
ljharb
left a comment
There was a problem hiding this comment.
I'm not sure I agree with the OP; but I also don't think it's a good use of time to polish the spec text for this proposal at this time, given that there may still need to be a lot of changes before it's viable.
1 task
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It doesn’t make sense to introduce a new specification type that is also an ECMAScript runtime Object value, so this changes it to use Records.
Also fixes #27
Depends on:
ecmarkup#35 (merged)[[ErrorData]]#36