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

editorial: add note about parsing #463

Merged
merged 2 commits into from
Jul 2, 2020
Merged

editorial: add note about parsing #463

merged 2 commits into from
Jul 2, 2020

Conversation

ryzokuken
Copy link
Member

Add a brief note to the specification about the reason for non-existence
of parsing functionality.

Fixes: #424

/cc @sffc @littledan

Add a brief note to the specification about the reason for non-existence
of parsing functionality.

Fixes: tc39#424
Copy link
Contributor

@sffc sffc left a comment

Choose a reason for hiding this comment

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

Thank you!

@anba
Copy link
Contributor

anba commented Jun 22, 2020

Neither ECMA-402 nor ECMA-262 directly address the reader ("you"), so the style for this note feels a bit unusual.

spec/overview.html Outdated Show resolved Hide resolved
Copy link
Member

@leobalter leobalter left a comment

Choose a reason for hiding this comment

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

as pointed out by @ljharb.

@ryzokuken I'd like your input in the proposed change before merging.

Thanks for this addition!

@leobalter
Copy link
Member

Let's see how it works using the PR tooling from GitHub...

@leobalter leobalter merged commit d0981ee into tc39:master Jul 2, 2020
@ryzokuken
Copy link
Member Author

Sorry @leobalter that you had to fix this up. I'd been planning to do it today 😅 Thanks!

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.

Explicitly state in the spec why we don't have parse methods
5 participants