On Wed, Dec 2, 2020 at 7:47 AM Ian Lance Taylor wrote:
>
> This Go frontend patch changes the parser to not advance past an
> unexpected semicolon, after it gives an error. We've already read the
> unexpected semicolon, so advancing again causes us to skip the next
> token, causing future errors
This Go frontend patch changes the parser to not advance past an
unexpected semicolon, after it gives an error. We've already read the
unexpected semicolon, so advancing again causes us to skip the next
token, causing future errors to be out of sync. Bootstrapped and ran
Go testsuite on x86_64-pc
