John,

js-loaders is both the initial spec. draft and the initial prototype of the module subsystem.  What we have now is the integration of the that initial draft into the actual ES6 spec.  In doing that there is some editorial renaming and refactoring intended to improve the spec. clarity and the logical layer of the entire ES6 spec.   There shouldn't be any semantic differences, except where there were ambiguities or open issues and those we will be discussing.

Issues relating to the specification need to go through bugs.emcascript.org so I can track and resolve them them for the official specification.  I just added a "modules" component to the "Draft for 6th Edition" product.  I suggest you run all feature/specification related issues through there.  Dave, Sam, and Jason will all be CC'd on those.

Issues relating specifically to Jason's prototype can probably continue to be handled on github.

Allen

On Jan 21, 2014, at 7:43 AM, John Barton wrote:

> 
> 
> 
> On Mon, Jan 20, 2014 at 7:42 PM, Allen Wirfs-Brock <allen at wirfs-brock.com> wrote:
> The draft is available at http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts#january_20_2014_draft_rev_22 
> 
> Big news: Promise and Module Loading/Linking.  Still a few loose ends, but we're getting there.
> 
>  Changes include:
> 
> Promises
> Module loading/linking semantics
> Internal Tasks
> Realm Objects
> Loader Objects
> We have been implementing module loading based on and giving feedback to https://github.com/jorendorff/js-loaders.  I was under the impression that the standards committee had temporarily delegated the module-loading to js-loaders. Were we wrong or can someone clarify what we should be paying attention to?
> 
> jjb  
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140121/fa8c02e4/attachment.html>

js-loaders is both the initial spec. draft and the initial prototype of the module subsystem.  What we have now is the integration of the that initial draft into the actual ES6 spec.  In doing that there is some editorial renaming and refactoring intended to improve the spec. clarity and the logical layer of the entire ES6 spec.   There shouldn't be any semantic differences, except where there were ambiguities or open issues and those we will be discussing.

Issues relating to the specification need to go through bugs.emcascript.org so I can track and resolve them them for the official specification.  I just added a "modules" component to the "Draft for 6th Edition" product.  I suggest you run all feature/specification related issues through there.  Dave, Sam, and Jason will all be CC'd on those.

Issues relating specifically to Jason's prototype can probably continue to be handled on github.