We had a discussion back in Feb about a potential Module.isModule function.
Since then, Module has been moved to being created through
Reflect.Loader.prototype.newModule.
So it sounds like a Reflect.isModule or Reflect.Loader.prototype.isModule
may be the way to go.
Which of these would be preferable?
This does affect code being output today through Traceur, so it would be
useful to know if we can implement something along these lines or not.
Thanks for feedback in advance.
Guy
We had a discussion back in Feb about a potential Module.isModule function.
Since then, Module has been moved to being created through
Reflect.Loader.prototype.newModule.
So it sounds like a Reflect.isModule or Reflect.Loader.prototype.isModule
may be the way to go.
Which of these would be preferable?
This does affect code being output today through Traceur, so it would be
useful to know if we can implement something along these lines or not.
Thanks for feedback in advance.
Guy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140916/0feaa6f6/attachment.html>
We had a discussion back in Feb about a potential Module.isModule function.
Since then, Module has been moved to being created through Reflect.Loader.prototype.newModule.
So it sounds like a Reflect.isModule or Reflect.Loader.prototype.isModule may be the way to go.
Which of these would be preferable?
This does affect code being output today through Traceur, so it would be useful to know if we can implement something along these lines or not.
Thanks for feedback in advance.
Guy