-
Notifications
You must be signed in to change notification settings - Fork 26
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
TC39 Meeting on May 2016 #38
Comments
Thanks, this is awesome! I will tweet about this tomorrow when I can do it earlier in the day US time. |
Thanks for the report, this is very useful. Regarding ES2016, what's a good resource to see what made it into the spec? |
Hi @leobalter. I have filed a couple of proposals ( |
@jzaefferer https://github.com/tc39/proposals/blob/master/finished-proposals.md I'll have to add a column for the year, but basically anything before the end of January YYYY, makes it into that year. |
So the only new feature in ES2016 is Array.prototype.includes? And ES2017 will have string padding and the others on that table? |
@jzaefferer also the exponentiation operator, but yes, exactly. |
The new features are Array#includes and the Exponentiation Operator. ES2016 has also got some new fixes from PRs from the tc39/ecma262's repo, but we need to find a better way to document this. |
@ljharb you got me by seconds |
All the current stage 3 proposals has a great chance to land on ES2017. On the stage 2 proposals I would like to see landing on ES2017: They have a good chance, but we can't say it will happen until it happens. |
@leobalter The report is super helpful and provided a different angle of insight than the meeting notes 👍 |
Thanks, @gsklee! I'm closing this issue as we can get ready for the next meeting report. |
There's a new report file on this repo with the highlights from the meeting that happened last month in Munich.
https://github.com/jquery-foundation/standards/blob/master/reports/TC39/2016-05.md
This report is opinionated - from my pov - and does not replace the meeting notes.
Please use this issue for comments.
Thanks @kborchers and @tkellen for reviewing it.
The text was updated successfully, but these errors were encountered: