Perhaps the silliest parse error in encore?

[TheGrandmother]

Writing this:

for x in [420 .. this.lol]

Will work.
But:

for x in [this.lol .. 420]

Will cause a parse error since encore didn't expect that first .

[supercooldave]

Should be pretty easy to fix. Dive in!

[EliasC]

Actually, this time I can understand why the parser is confused! It reads this . lol, so obviously it's parsing a path, so the next dot is also part of it, but then when it's expecting an identifier there's another dot! "Obviously there's something wrong" thinks the parser, and is unaware that the one who is wrong is the parser itself...

Try making .. a reservedOp in the parser!

[TheGrandmother]

@EliasC

and is unaware that the one who is wrong is the parser itself...

I fear the day when the Encore parser becomes self-aware.

tried making .. a reservedOp but that didn't fix it.
I didn't have much time to look into it last night but I'll examine it further when I get to school.