Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Stage 2 tracking #14

Closed
4 tasks done
bakkot opened this issue Mar 20, 2018 · 6 comments
Closed
4 tasks done

Stage 2 tracking #14

bakkot opened this issue Mar 20, 2018 · 6 comments

Comments

@bakkot
Copy link
Collaborator

bakkot commented Mar 20, 2018

This proposal achieved stage 1 at the March 2018 meeting. This is a tracking issue for getting stage 2.

(I don't believe there's anything more which is strictly required and not yet done except to bring it before the committee again, though a few minor things would be good to get done.)

  • Initial spec text
  • Major syntax and semantics
  • Document several motivating use cases
  • Transfer this repo to the TC39 org
@ljharb

This comment has been minimized.

@ljharb
Copy link
Member

ljharb commented Apr 14, 2018

The minor question of the second argument (#13) is something that I think can wait for a followon proposal, unless the committee feels strongly about one of the three directions (no 2nd arg ever, proto, or mapper).

@bathos
Copy link
Collaborator

bathos commented Apr 14, 2018

I agree that it’s not essential to the proposed functionality. However I don’t know of any precedent cases for functions whose signatures were expanded after introduction — has that been done before, and would it be considered a backwards incompatibility risk?

@ljharb
Copy link
Member

ljharb commented Apr 14, 2018

That’s a fair point, and something I’ll bring up in committee.

Regardless, i think “one arg ever” is still valuable enough to proceed as such, since you can use setPrototypeOf/proto for the proto case and .map for the mapper case if needed.

@bakkot
Copy link
Collaborator Author

bakkot commented May 22, 2018

For posterity, here's the slides from the stage 1 presentation.

@bakkot
Copy link
Collaborator Author

bakkot commented May 22, 2018

This achieved stage 2 at the May 2018 meeting!

@bakkot bakkot closed this as completed May 22, 2018
@bakkot bakkot mentioned this issue May 22, 2018
8 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants