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

[Meta] Array.prototype.sample #23

Closed
leobalter opened this issue Apr 23, 2016 · 8 comments
Closed

[Meta] Array.prototype.sample #23

leobalter opened this issue Apr 23, 2016 · 8 comments
Labels

Comments

@leobalter
Copy link
Collaborator

leobalter commented Apr 23, 2016

The Array#sample proposal will be introduced to TC39 potentially in the next meeting.

I might champion it, and the work there is currently made by @tkellen and @ashleygwilliams.

Every feedback there is important, thanks!

@leobalter leobalter added the TC39 label Apr 23, 2016
@jzaefferer
Copy link
Collaborator

Could you add a link?

@leobalter
Copy link
Collaborator Author

I missed the link: https://github.com/awtk/Array.prototype.sample

@tkellen
Copy link

tkellen commented Apr 29, 2016

thanks @leobalter! Once I understand how this process works I would love to follow up with more proposals 💃

@ashleygwilliams
Copy link

yes! whoa blast from the past here, but yes yes this is cool and i would love to be involved in more stuff like this!

@leobalter
Copy link
Collaborator Author

Before I move this forward, we have to fill some gaps:

  1. First and most important, we need to fill the proposal with use cases, covering where this method would be useful as a native resource and any pain points it address.
  2. We need to set spec steps for it.
  3. We need to bring this to the esdiscuss mailing list for a pre-discussion and collect more feedback.

After these are done, I'll be able bring this to a meeting without a high risk of rejection.

@tkellen
Copy link

tkellen commented Apr 29, 2016

Thanks for the guidance @leobalter! @ashleygwilliams you wanna schedule an hour working meeting next week sometime to try to address those things? If yeah, I'll ping you on email :D

@ashleygwilliams
Copy link

yes def, @tkellen!

@leobalter
Copy link
Collaborator Author

As in the same reasons I mentioned on #33, this won't make it to the stage process for now. I'm sorry for this bit of frustration as I share at this moment, but there's not much I can do to make this part of the specs for now.

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

No branches or pull requests

4 participants