At present, we are pretty close to the default error handling in SLY, which is not very helpful.
We have a very simple custom error handler in the lexer which prints a message when tokenizing fails. It may be possible to do better than this.
We have no custom error error handler in the parser, and the default one doesn't emit much useful information. We may do better than this.
We also have no error recovery in the parser. This may or may not be feasible to improve: the cell_methods language has very few markers that permit skipping to the next parseable "statement" (Semicolons between cell methods would have been a good idea for several reasons. I'm lookin' at you, CF Conventions.)
At present, we are pretty close to the default error handling in SLY, which is not very helpful.
We have a very simple custom error handler in the lexer which prints a message when tokenizing fails. It may be possible to do better than this.
We have no custom error error handler in the parser, and the default one doesn't emit much useful information. We may do better than this.
We also have no error recovery in the parser. This may or may not be feasible to improve: the cell_methods language has very few markers that permit skipping to the next parseable "statement" (Semicolons between cell methods would have been a good idea for several reasons. I'm lookin' at you, CF Conventions.)