Has there been any further discussion on this? It would be good to know the
form so that ES6 modules currently being generated today will not break in
real ES6 environments.
On 21 February 2014 13:30, David Herman wrote:
> OK, we can discuss and report back. We'll definitely want to take into
>
OK, we can discuss and report back. We'll definitely want to take into account
Guy's use case about being able to recognize module instance objects as such.
Dave
On Feb 21, 2014, at 12:53 PM, Allen Wirfs-Brock wrote:
>
> On Feb 21, 2014, at 12:08 PM, David Herman wrote:
>
>> I think it shoul
On Feb 21, 2014, at 12:08 PM, David Herman wrote:
> I think it should be Module.isModule.
I don't think we actually need something named Module, but that's a separate
conversation I have in the queue to have with you.
But food for thought: for module loader reflection purposes, it would be be
: es-discuss
> Subject: Re: Detecting a Module object
>
> I think it should be Module.isModule.
>
> Dave
>
> On Feb 21, 2014, at 10:57 AM, Allen Wirfs-Brock wrote:
>
>> it's not going to be instanceof for various technical reasons.
>>
>>
Is Module a global now?
From: es-discuss on behalf of David Herman
Sent: Friday, February 21, 2014 15:08
To: Allen Wirfs-Brock
Cc: es-discuss
Subject: Re: Detecting a Module object
I think it should be Module.isModule.
Dave
On Feb 21, 2014, at 10:57
I think it should be Module.isModule.
Dave
On Feb 21, 2014, at 10:57 AM, Allen Wirfs-Brock wrote:
> it's not going to be instanceof for various technical reasons.
>
> I suspect, we can have a isModule predicate function somewhere. Perhaps,
> Reflect.isModule or Reflect.Loader.isModule...
>
it's not going to be instanceof for various technical reasons.
I suspect, we can have a isModule predicate function somewhere. Perhaps,
Reflect.isModule or Reflect.Loader.isModule...
Allen
On Feb 21, 2014, at 3:53 AM, Guy Bedford wrote:
> Being able to do `m instanceof Module` is certainly a
Being able to do `m instanceof Module` is certainly a lot nicer here though.
Just to return to the consideration of modules as classes, I still don't
understand what the major issue is with having a module as a class without
any prototype methods.
On 21 February 2014 00:07, Guy Bedford wrote:
Thanks John for explaining. As for the usefulness of this path as I say it
is yet to be determined.
Specifically the ability to detect a module instance is needed to allow ES6
loaders to load AMD that was transpiled from ES6 into AMD.
It may be a little bit of an obscure use case, the exact detai
On Thu, Feb 20, 2014 at 1:01 PM, Allen Wirfs-Brock wrote:
>
> On Feb 20, 2014, at 12:53 PM, Guy Bedford wrote:
>
> > Thanks, if there is some way to detect this it may well be useful.
> >
> > The use case I came across it was trying to allow ES6 modules to be
> transpiled into AMD for use in an ES
On Feb 20, 2014, at 12:53 PM, Guy Bedford wrote:
> Thanks, if there is some way to detect this it may well be useful.
>
> The use case I came across it was trying to allow ES6 modules to be
> transpiled into AMD for use in an ES6 loader. I'm still not sure how
> necessary the use case is, but
Thanks, if there is some way to detect this it may well be useful.
The use case I came across it was trying to allow ES6 modules to be
transpiled into AMD for use in an ES6 loader. I'm still not sure how
necessary the use case is, but it definitely would need this functionality
work.
On 20 Febru
On Feb 20, 2014, at 11:47 AM, Guy Bedford wrote:
> If Module objects are not classes, then what would be the recommended way to
> detect if a given object is a Module?
>
> Would there be a unique toString output?
Can't. 'toString' might be a binding exported by a module so a module object
ca
If Module objects are not classes, then what would be the recommended way
to detect if a given object is a Module?
Would there be a unique toString output?
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
14 matches
Mail list logo
