Kevin Gibbons

It does not introduce a new rule to follow.

Dug up where this change was introduced: https://github.com/domenic/promises-unwrapping/issues/105 The concern was specifically that `Promise.resolve(foo)` could break invariants in the surrounding code. That's already out the window because of the synchronous...

Another alternative fast-path would be to use the same test as `Promise.resolve` and `await`: before reading `resolution.then`, first test `IsPromise(resolution) && resolution.constructor === Promise`, and if that passes then invoke...

@rbuckton I've been thinking about this again recently, and it occurred to me you might have things you'd like to see included for use in your vscode plugin. Right now,...

Maybe internal methods, too.

I think this is just a matter of ``'ing "String constructor" somewhere.

I'm also partial to [rust's `macro!` syntax](https://doc.rust-lang.org/rust-by-example/macros.html), though @michaelficarra said he'd prefer something without a new sigil.

`ReturnIfAbrupt` has the same issue, yes.

@michaelficarra do you have a prose form in mind for, e.g., IfAbruptRejectPromise?

Are you interested in having - current editors - current and former editors, or - all contributors? The current editor support is aimed at just the first. And we haven't...