stop keyword parse error causes additional errors at end of file

[TwitchBronBron]

When the stop keyword parse error is encountered (see #192), and when there is nothing else in the body of the method, it causes a strange extra error to show up at the end of the file:

Adding any valid line after the stop keyword seems to mitigate the issue.

Is there a way to restrict this error so that it doesn't cause additional errors later in the document?

[sjbarag]

The solution will be twofold here:

1. Fix Stop keyword causes parse errors #192 "Stop keyword causes parse errors"
2. Some work in Better recovery after errors #157 to make the synchronize() function a bit less greedy (details TBD at a later date though)

Thanks for striving for a good developer experience, @TwitchBronBron! I really appreciate it 😄

[TwitchBronBron]

PR #214 seems to have fixed this issue.