Any reason template string with empty interpolation placeholder (`${}`) throws?

Caitlin Potter caitpotter88 at gmail.com
Fri Oct 23 00:34:15 UTC 2015


Okay, but usability wise, this kind of sucks. There's a reason it's not what people expect, and why other languages with string interpolation behave differently.

> On Oct 22, 2015, at 8:24 PM, Allen Wirfs-Brock <allen.wirfsbrock at gmail.com> wrote:
> 
> 
>> On Oct 22, 2015, at 4:55 PM, Mark Miller <erights at gmail.com> wrote:
>> 
>> 
>> 
>> On Thu, Oct 22, 2015 at 7:20 PM, Caitlin Potter <caitpotter88 at gmail.com> wrote:
>>> Cute, but nobody is realistically going to do that.
>> 
>> Since `${}` is a static error, what do you realistically think people will do? Especially if they meant `${''}`, how do you expect them to react to the static error?
> 
> Just like they do if they have a line of code that reads:
> 
> ```js
> str = ;
> ```
> 
> when they meant
> 
> ```js
> str = ‘’;
> ```
> 
> It’s just a syntax error.  I probably have syntax errors in 50% of the lines that I initially type.  I parse, and then fix.
> 
> Allen
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20151022/853543bc/attachment.html>


More information about the es-discuss mailing list