Hi Mark,
Thanks for kickstarting this proposal. Initial comments:
- The keyword 'mixin' could be confusing. It is used to express trait
composition, not mixin composition. A better alternative would be compose.
If we want to stick to reserved keywords, implements seems the most
appropriate
On 2010-09-14, at 04:56, Tom Van Cutsem wrote:
If we want to stick to reserved keywords, implements seems the most
appropriate (although this similarly confuses trait composition with
interface implementation).
Alternatively, you could repurpose the (now disparaged) `with` keyword. That's
On 14.09.2010 1:03, Mark S. Miller wrote:
On Mon, Sep 13, 2010 at 2:02 PM, Mark S. Miller erig...@google.com
mailto:erig...@google.com wrote:
On Mon, Sep 13, 2010 at 1:18 PM, Dmitry A. Soshnikov
dmitry.soshni...@gmail.com mailto:dmitry.soshni...@gmail.com
wrote:
I didn't
On Tue, Sep 14, 2010 at 4:47 AM, P T Withington p...@pobox.com wrote:
On 2010-09-14, at 04:56, Tom Van Cutsem wrote:
If we want to stick to reserved keywords, implements seems the most
appropriate (although this similarly confuses trait composition with
interface implementation).
In the
On Tue, Sep 14, 2010 at 8:46 AM, Mark S. Miller erig...@google.com wrote:
Btw, the current proposal does currently repurpose with for renamings.
Even though there's no syntactic conflict, if we use with instead of
mixin we should choose a different syntax for renamings. Suggestions?
as.
Mike
On Tue, Sep 14, 2010 at 6:37 AM, Dmitry A. Soshnikov
dmitry.soshni...@gmail.com wrote:
On 14.09.2010 1:03, Mark S. Miller wrote:
On Mon, Sep 13, 2010 at 2:02 PM, Mark S. Miller erig...@google.comwrote:
On Mon, Sep 13, 2010 at 1:18 PM, Dmitry A. Soshnikov
dmitry.soshni...@gmail.com wrote:
On 14.09.2010 20:19, Mark S. Miller wrote:
On Tue, Sep 14, 2010 at 6:37 AM, Dmitry A. Soshnikov
dmitry.soshni...@gmail.com mailto:dmitry.soshni...@gmail.com wrote:
On 14.09.2010 1:03, Mark S. Miller wrote:
On Mon, Sep 13, 2010 at 2:02 PM, Mark S. Miller
erig...@google.com
The note in section 14.1 advises: If an appropriate notification mechanism
exists, an implementation should issue a warning if it encounters in a
Directive Prologue an ExpressionStatement that is not a Use Strict Directive or
which does not have a meaning defined by the implementation.
It
8 matches
Mail list logo