[strawman] Symbol.thenable proposal
me at gus.host
Sat Apr 14 20:25:40 UTC 2018
It's a fair point, i assume the usage would be like if the property
exists then ignore thenable behaviour and if it is falsy then none of
any of this behaviour would occur, so a Module Namespace Object could
have like [whateverSymbolName]: null, if thats sorta what you are proposing?
On 2018-04-14 13:11:34, Michael Theriot wrote:
> A hypothetical proposal addressing that would intersect with this.
> On Sat, Apr 14, 2018 at 2:01 PM, <me at gus.host <mailto:me at gus.host>> wrote:
> I don't understand why you would expect that, can you explain a bit
> On 14 Apr 2018 10:53, Michael Theriot <michael.lee.theriot at gmail.com
> <mailto:michael.lee.theriot at gmail.com>> wrote:
> Currently 'then' is effectively a reserved key and I'd expect
> any extension that allows the language to ignore it likewise
> include a means of changing the key entirely.
> On Apr 12, 2018, at 9:33 PM, Gus Caplan <me at gus.host
> <mailto:me at gus.host>> wrote:
> Hello all,
> In an effort to curtail the interesting behavior of
> Promise.resolve (especially
> with regard to dynamic import), I have created a proposal
> for a well-known
> symbol which will allow an object to not be treated as a
> I am privy to the current protocol proposal which might be a
> better fit for
> this, but due to dynamic import already being stage 3, I
> don't feel we should
> wait for it to come to fruition.
> Comments and suggestions are of course quite welcome at the
> repo .
> : https://github.com/devsnek/proposal-symbol-thenable
> es-discuss mailing list
> es-discuss at mozilla.org <mailto:es-discuss at mozilla.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the es-discuss