babel
June 2019
Dynamic imports moves to stage 4 🎉 (pending editors reviewing the spec PR)
https://github.com/babel/babel/pull/9552
Let all early errors be SyntaxErrors gained consensus
https://github.com/tc39/ecma262/pull/1527
For-in enumeration order reached Stage 2
https://github.com/tc39-transfer/for-in-exploration/
BigInt to Stage 4, pending editors reviewing the spec PR
https://github.com/tc39/proposal-bigint/
eval(nonString) should not side effect gained consensus
https://github.com/tc39/ecma262/pull/1504
Set "name" property for anonymous functions gained consensus
https://github.com/tc39/ecma262/pull/1490
Array.isTemplateObject to Stage 2
https://github.com/mikesamuel/proposal-array-is-template-object
Lookup constructor.resolve only once in PerformPromise{All, Race} got consensus
That seems silly don't write about it since those proposals claimed to change the state at this meeting.
They sought advancement on the agenda; but not everything that seeks it gets it.
The purpose of this issue isn’t to update people on the meeting - that’s what the notes are for. It’s to let Babel people know what actions they might need to take as a result of the meeting.
@ljharb I can't understand, is it too hard to write the summary of the result of discussion for each proposal from the agenda? I'm one of the first implementors of proposals - and since I haven't any direct information from TC39 meetings, I should keep in mind that the state of the proposal was able to be changed and just someone forgot to publish it here or somewhere else until the publication of notes in the meeting notes repo.
Yes, it is - the agenda has many things on it, and the notes - which you just have to wait for - are that writeup.
The tc39/proposals repo is the closest thing to a source of truth; that's where it will be up to date after every meeting.
...which also contains obsolete information and updated with a delay.
Awesome, thanks.
What information in it is obsolete? and yes, a delay is fine - there's no rush on adapting to these changes.
I wrote issues or messages to required people about obsolete information in tc39/proposals repo enough. But now I write about this repo as about a place where I can get immediate information about changes in states of proposals for planning releases / changes in core-js. I can't understand, it's too hard to write just some words that after discussing the state of the proposal was not updated? It could be very useful to me.
If you don't see a message saying it was updated, then it wasn't updated. I'm not sure what's so hard about that.
The proposals repo is fully up to date. If you have an issue to file, please file it, but otherwise whatever's in that repo is the state of all proposals.
If you don't see a message saying it was updated, then it wasn't updated.
See the previous issues - not all updates were published here. Otherwise, such questions would not arise.
The proposals repo is fully up to date.
Also not always.
I'm the one tasked to keep it so; and yes, it is up to date, as far as I'm aware.