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

[spec] add builtin matchers with proper semantics and location #263

Merged
merged 1 commit into from
Jul 8, 2022

Conversation

ljharb
Copy link
Member

@ljharb ljharb commented Jul 8, 2022

Followup to #262.

I will file issues for the open questions contained herein:

  1. Error subclasses: how are they checked?
  2. Promise: should we accept thenables? Current semantics are "IsPromise", ie, internal slot.
  3. other constructors, in the last clause section marked "TODO"

There's spec TODOs for me for:

  1. the RegExp.prototype builtin matcher
  2. builtin matchers for relevant boxed primitives (that have the same semantics primitives will be hardcoded to have)
  3. the [[TypedArrayName]] comparison needs tightening up

I'm going to merge this ASAP; we can iterate later.

@ljharb ljharb force-pushed the builtinMatchers branch from 9f45d6a to f9d30e9 Compare July 8, 2022 03:51
@ljharb ljharb merged commit f9d30e9 into main Jul 8, 2022
@ljharb ljharb deleted the builtinMatchers branch July 8, 2022 05:02
@github-pages github-pages bot temporarily deployed to github-pages July 8, 2022 05:03 Inactive
Comment on lines +1039 to +1040
<emu-clause id="sec-placeholder"><h1>Placeholder to ensure correct clause numbering</h1></emu-clause>
Copy link
Member

Choose a reason for hiding this comment

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

ecmarkup will warn about duplicated clause ids.

Copy link
Member Author

Choose a reason for hiding this comment

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

yes, i'm aware, but until ecmarkup supports arbitrary numbering, this is the only technique i've found, and we'll just have to ignore the warnings. cc @bakkot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants