On Wed, Jul 10, 2013 at 10:46 PM, Allen Wirfs-Brock
<allen at wirfs-brock.com> wrote:
>
> On Jul 10, 2013, at 9:39 PM, Andrew Fedoniouk wrote:
>
...
>
> The problem with this construction: it's the only feature in ES syntax
> so far that
>
>
> no, it also occurs between object literals and destructuring assignment
> object patterns.

So that "fat arrow" and peculiar destructing assignment are the only features
that trigger such spike in syntax complexity?

Will language survive without these two?

>
> requires compiler to use full AST implementation at compilation phase.
>
>
> you don't necessarily have to built a full AST.  In some cases you will need
> to at least do multiple parses of the same text.

Hmm... I see that while getting '(' you will need that double
parsing almost always.

>
> Is that arrow syntax still debatable?
>

Too pity.

>
> Yes, but primarily in the sense that such issues were already considered.
>

Did we consider green gases emission increase that will happen due to that
 double parsing of code that currently is parsed strictly once?

( Consider that rhetoric question above as just a reminder that ES6
  parser will be used for existing web code when it will deployed for
  pretty much each connected machine and device ).

--
Andrew Fedoniouk.

http://terrainformatica.com

On Wed, Jul 10, 2013 at 10:46 PM, Allen Wirfs-Brock <allen at wirfs-brock.com> wrote:

> no, it also occurs between object literals and destructuring assignment object patterns.

So that "fat arrow" and peculiar destructing assignment are the only features
that trigger such spike in syntax complexity?

Will language survive without these two?

> you don't necessarily have to built a full AST.  In some cases you will need
> to at least do multiple parses of the same text.

Hmm... I see that while getting '(' you will need that double parsing almost always.

> Is that arrow syntax still debatable?

Too pity.

> Yes, but primarily in the sense that such issues were already considered.

Did we consider green gases emission increase that will happen due to that double parsing of code that currently is parsed strictly once?

( Consider that rhetoric question above as just a reminder that ES6
  parser will be used for existing web code when it will deployed for
  pretty much each connected machine and device ).