Should ES6 global variable "Promise" be changed in examples in the docs?

With ES6 coming and Promise being a reserved keyword in ES6, should we encourage users to use a different variable (other than Promise) when using Bluebird? Bluebird seems like a good replacement candidate.

I’d be willing to do a PR if others think this is a good idea. I would have thought it’d been brought up before, but couldn’t find a ticket. I’m still wondering if there is some other reason it hasn’t been changed, so I wanted to ask before taking the time to do a PR (since it’s not quite as simple as just finding and replacing).

[CWSpear]

Man, if I had a dime for everytime I got a message like this (this one is copy and pasted from earlier today):

@cwspear I just spent like 30 mins debugging cus I didn’t import bluebird, and it defaulted to the native Promise… noob mistake.

These kinds of issues will always exist, but can be minimized with the official docs championed const Bluebird = require('bluebird');, etc.

[bergus]

Promise is not a reserved keyword. It’s the name of a built-in object, the identifier for a global variable. Shadowing it is not a problem, it actually is what we aim to do here.