V8's native Promise misbehaves when resolved with a thenable

[Arnavion]

I see the v4 post is promoting V8 promises, so just wanted to make sure this issue is on your radar for LTS considerations.

https://code.google.com/p/v8/issues/detail?id=4162

More discussion and test case in zloirock/core-js#78

[domenic]

/cc @littledan who I know was looking for promise issues that are causing pain in the wild.

[ChALkeR]

@Fishrock123 Are we promoting V8 promises?

[Arnavion]

https://nodejs.org/en/blog/release/v4.0.0/

Node.js v4.0.0 contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new ES6 features that are enabled by default including block scoping, classes, typed arrays (Node's Buffer is now backed by Uint8Array), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and, new to V8 v4.5, arrow functions.

[Fishrock123]

What, should we pretend they don't exist? I wouldn't say we are promoting them though. I'd definitely not recommend using native promises, at least for now.

Actually let's just override the global variable for 5.x+

[littledan]

Thanks for the bug report and drawing my attention to it. This looks pretty significant. Sorry it hasn't been addressed so far.

[jasnell]

Closing as the originally reported issue (https://code.google.com/p/v8/issues/detail?id=4162) appears to have been fixed.

[littledan]

Thanks again for the bug report; please let me know if you have any more issues with Promises.