My sense, from the informal discussions about this at the TC39 meeting, is that 
most of us would hope that new WebIDL abstractions follow the ES6 class 
conventions and that existing WebIDL, because of legacy constrants  abstraction 
are likely not to migrate to the ES6 class conventions. 

Syntactically, in WebIDL, you would presumably need an attribute or something 
to indicate which set of conventions to use for any particular interface.

Allen 
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to