Editorial: replace use of Type macro #902
Merged
Conversation
This file contains 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
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.
Type()is kind of a weird operation; it's not totally clear whatTypewould return for an arbitrary Record. For example, Completion Records are listed as specification types, so wouldType(_cr_)be "Record" or "Completion Record"? tc39/ecma262#3339 will clarify this, but will do so by precisely defining the domain of input to be only ES language types, not specification types.In any case, it's also not necessary to use the macro here; the prose is easier to read anyway. This was the only use of this AO in 402.