Proposal: No LineTerminator should be allowed between {CallExpression, MemberExpression} TemplateLiteral

The connection between a CallExpression/MemberExpression and a
TemplateLiteral does not requires delimiters. They are both common and
allowed independently. CallExpression / MemberExpressions are allowed to
end a statement and TemplateLiterals are allowed to start a statement. When
adopting "semicolon free" style, it will become a problem because the
connection between the two is not visually clear if there's a new line
between them.

I propose we add a [No LineTerminator here] between
CallExpression/MemberExpression and TemplateLiteral.

Thanks,
Bei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150213/79de6f97/attachment.html>

Good observation. I agree.

Date: Fri, 13 Feb 2015 15:39:29 -0800
Subject: Proposal: No LineTerminator should be allowed between	{CallExpression, MemberExpression} TemplateLiteral
From: ikarienator at gmail.com
To: es-discuss at mozilla.org

The connection between a CallExpression/MemberExpression and a TemplateLiteral does not requires delimiters. They are both common and allowed independently. CallExpression / MemberExpressions are allowed to end a statement and TemplateLiterals are allowed to start a statement. When adopting "semicolon free" style, it will become a problem because the connection between the two is not visually clear if there's a new line between them.
I propose we add a [No LineTerminator here] between CallExpression/MemberExpression and TemplateLiteral.
Thanks,Bei

_______________________________________________
es-discuss mailing list
es-discuss at mozilla.org
https://mail.mozilla.org/listinfo/es-discuss 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150214/f4bbcdf0/attachment.html>

>
>
> I propose we add a [No LineTerminator here] between
> CallExpression/MemberExpression and TemplateLiteral.
>

This would be inconsistent, since there are no such restrictions between
member expression or call expression components otherwise.  For example, in:

    foo
    (bar)

and

    foo
    [bar]

there is no semicolon insertion.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150213/0acfeb29/attachment.html>

The difference is the uncommon delimiter of the argument lists. If the
template literal must be surrounded by a pair of parentheses it will become
more visually significant. Since it's not, I think not allowing the line
terminator is reasonable.

On Sat, Feb 14, 2015 at 1:41 PM, Shinji Ikari <ikarienator at gmail.com> wrote:

> Ah yes! I will resend.
>
> On Fri, Feb 13, 2015 at 20:54 Kevin Smith <zenparsing at gmail.com> wrote:
>
>> Hey there!  Did you mean to reply to the list?
>>
>> On Fri, Feb 13, 2015 at 11:53 PM, Shinji Ikari <ikarienator at gmail.com>
>> wrote:
>>
>>> The difference is the uncommon delimiter of the argument lists. If the
>>> template literal must be surrounded by a pair of parentheses it will become
>>> more visually significant. Since it's not, I think not allowing the line
>>> terminator is reasonable.
>>>
>>> On Fri, Feb 13, 2015 at 20:29 Kevin Smith <zenparsing at gmail.com> wrote:
>>>
>>>>
>>>>> I propose we add a [No LineTerminator here] between CallExpression/
>>>>> MemberExpression and TemplateLiteral.
>>>>>
>>>>
>>>> This would be inconsistent, since there are no such restrictions
>>>> between member expression or call expression components otherwise.  For
>>>> example, in:
>>>>
>>>>     foo
>>>>     (bar)
>>>>
>>>> and
>>>>
>>>>     foo
>>>>     [bar]
>>>>
>>>> there is no semicolon insertion.
>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150215/7778c6dd/attachment.html>