Should we distinguish between accepted and pending ES6 features?

[mathiasbynens]

Should we distinguish between accepted and pending ES6 features?

Things like String.prototype.at and Function.create are not in the latest ES6 draft (yet). Some are just proposals, that will never make it to the spec (or to browsers). IMHO it’s useful to include them in the list, but maybe we should add mark them as “not really ES6 (yet)”?

[addyosmani]

I agree completely. We could move them into a 'pending' or 'under consideration' bucket.

[paulirish]

Browser/node support seems more relevant than spec status so.. Its a challenge to see how specific you want to be. ;)

[mathiasbynens]

@paulirish Yeah but these things definitely won’t make it into browsers until they are added to the draft spec. They’re just proposals (some of which TC39 agrees with) at this point.

I know this from experience — I’ve been trying to get a patch that implements String.fromCodePoint and String.prototype.codePointAt (both of which have been in the draft spec for ages) to land in V8 — behind the --harmony flag, even — and it’s haaaaaard, but for very good reasons.

The features this issue is about are not even in the draft spec or accepted by TC39, so I seriously doubt they’ll show up in any native implementation.

I’ve edited the top post so it’s a bit clearer, hopefully. Thanks for the feedback!