>
> By the way, I noticed that duck typing here is *already* not done with
> symbols. So the argument isn't "its either going to be symbols or nothing".
> Its "its either going to be symbols or the method then".
That's right, and (digging a little deeper) there are two problems with
using symbols:
1. Given that DOM wants Promises ASAP, I'm pretty sure they don't want a
dependency on ES6-only symbols.
2. Duck-typing symbols need to work cross frame, which means either:
a) we need System.then added to the spec.
b) we need the cross frame symbol registration thing in place (i.e.
Symbol.for("then")).
Now Promises are by design "pointer-like": featureless indirectors, if you
will. So nominal (non-duck) typing should work just fine for this case.
And if nominal typing works, then we can avoid these language-feature
dependency problems.
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
