Report multiple parse errors

[eaburns]

On error, try to synchronize to the next statement in a block of statements and continue. Need to pay attention to things like opening blocks and semicolons that aren't statement terminating, like those inside of for loops.

[mccoyst]

We've argued about this before, but I've always found this to be limitedly useful, especially for parsing errors, because most of the errors that follow are usually caused by the first one, so I have to recompile after fixing it anyhow.

But I won't stop you~

[eaburns]

I'm surprised if we argued about this, because I agree with you on the topic: parse error are basically fatal. However, modern compilers seem to do a fine job at recovering from certain types of parse errors. No reason that Stop can't do just as well for some small set of cases. Synchronizing to the next statement in a block of statements seems reasonable to me, and I think that is what the standard Go parser does.

Anyway, don't worry too much. I consider this bug as having very low priority.

[mccoyst]

Maybe we just agreed loudly.