I really didn't mean to suggest any particular name, just that an imperative form should be provided or every lib will roll their own. On Tue, May 14, 2013 at 1:45 PM, Rick Waldron <waldron.rick@gmail.com>wrote: > > > > On Tue, May 14, 2013 at 4:01 PM, Scott Miles <sjmiles@google.com> wrote: > >> I can't think of any reason I would want to be able to mess with an >> import link ex-post-facto and have it do anything. I would also expect any >> registrations to be final and have no particular connection to the link tag >> itself. >> >> Now, this may be tangential, but users definitely need a way of loading >> imports dynamically. I believe the current gambit would be to inject a >> fresh link tag into head, which seems like the long way around Hogan's barn. >> >> I've been meaning to ask about the possibility of an imperative 'import' >> method. >> > > "import" is a FutureReservedWord that will be a Keyword as of ES6, so this > "import" method would have to be a method of some platform object and not a > method on [[Global]] object. > > > Rick > >
Received on Tuesday, 14 May 2013 21:13:07 UTC