Keeping js-sys bindings up to date

[bakkot]

(Please forgive the drive-by comment.)

I'm curious if there's a process for keeping the work done in #275 up to date as JavaScript evolves. For example, the Array.prototype.{flat,flatMap} proposal is in all major browsers and will probably reach stage 4 of the TC39 process next week, at which point it will (shortly thereafter) land in the living version of ECMA262 and subsequently ship in the ES2019 edition of the spec. Is there a way for people to tell if this project provides bindings for those functions?

If there's not something similar in place already, I think it would be useful for this project to have something like Babel's proposals tracking repo to note which things are implemented.

Personally I'd recommend that stage 4 be considered the appropriate time to ship bindings. (I am on TC39, but am not speaking for the rest of the committee.)

PS: The link in CONTRIBUTING.md is broken.

[fitzgen]

(Please forgive the drive-by comment.)

No need to apologize; great point to bring up!

We don't have a process yet, but it is a something we need to figure out!

I agree that stage 4 makes sense, since they are shippuing and expected to be in the next release of the standard. Stage 4 seems like something you can fairly reliably program against.

Assuming that stage 4 makes sense to @alexcrichton and others, then I think we can document this somewhere in the js-sys contributing docs.

PS: The link in CONTRIBUTING.md is broken.

Thanks for the heads up!

[alexcrichton]

Adding stage 4 apis sounds great to me! I'd be totally down for such a strategy