That case we can simply allow TemplateLiteral in Arguments. It will become more consistent as well and causes less cognitive burden. We don't even need to define MemberExpressionTemplateLiteral and CallExpression TemplateLiteral any more. BTW, the only places where Arguments is referred to are MemberExpression, CallExpression, and SuperCall.
Although it will be a rather breaking change because it will change the precedence of expressions. For example, currently new a`x` is a NewExpression. a`x` will be evaluated first. But with this change, it will also be a simple MemberExpression. The a method will be [[Construct]] ed with "x" as arg. On Fri, Feb 13, 2015 at 8:01 PM, Gary Guo <[email protected]> wrote: > If super TemplateLiteral is added, I will suggest we add new > MemberExpression TemplateLiteral, which might be more useful in practice. > > ------------------------------ > Date: Fri, 13 Feb 2015 20:55:49 -0500 > Subject: Re: TemplateLiteral tagged with super > From: [email protected] > To: [email protected] > CC: [email protected] > > > > But what would it be good for. Can anybody think of a practical use > case for this? > > I can't. And for what it's worth I didn't find *any* semantics obvious. I > think in general it's best to limit the contexts in which super can occur, > since it has different meanings depending on context. > > Seems like a "defer" thing to me. > > _______________________________________________ es-discuss mailing list > [email protected] https://mail.mozilla.org/listinfo/es-discuss > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
