What are the use cases for things like 'isGenerator'. When and why would
you need to know that an object upon which you are going to invoke the
Iterator interface was/wasn't implemented by a generator.
[`co`][1] is a library similar to Task.js that allows you to use ES6
generators as async /
Le 02/11/2013 03:13, Allen Wirfs-Brock a écrit :
On Nov 1, 2013, at 6:05 PM, David Bruant wrote:
I'm not sure about proxy returning Proxy as tag name. Is that a good idea?
Brand feels like something that could safely transparently cross proxies.
There is a note on in the ES6 draft on that
On Nov 1, 2013, at 7:13 PM, Allen Wirfs-Brock wrote:
On Nov 1, 2013, at 6:05 PM, David Bruant wrote:
Le 02/11/2013 01:08, Brandon Benvie a écrit :
On 11/1/2013 4:59 PM, Brandon Benvie wrote:
On 11/1/2013 4:31 PM, Brandon Benvie wrote:
In the spec for Object.prototype.toString:
'If
On Sat, Nov 2, 2013 at 10:55 AM, Allen Wirfs-Brock al...@wirfs-brock.comwrote:
[...] If the reasons for removing Proxy.isProxy are valid then we should
be providing such a backdoor.
not?
--
Cheers,
--MarkM
___
es-discuss mailing list
On Nov 2, 2013, at 11:25 AM, Mark S. Miller wrote:
On Sat, Nov 2, 2013 at 10:55 AM, Allen Wirfs-Brock al...@wirfs-brock.com
wrote:
[...] If the reasons for removing Proxy.isProxy are valid then we should be
providing such a backdoor.
not?
shouldn't
--
Cheers,
On Oct 25, 2013, at 7:49 PM, Allen Wirfs-Brock al...@wirfs-brock.com wrote:
It turns out that even in pseudo code, this is a fairly complicated set of
runtime validation rules to apply. I'm having a hard time convincing myself
that the runtime computational and meta data costs of this
6 matches
Mail list logo
