You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started using Farkle to build a parser for a programming language. I'm happy with the library and the results I'm getting, so thanks for working on it!
One thing that's not very clear to me is how to do error recovery with Farkle – with parser generators a-la yacc/bison/menhir I have access to 'error' productions; by inserting it in strategic places I can make the parser parse as much as possible while accumulating parse errors. Is there a similar mechanism in Farkle?
The text was updated successfully, but these errors were encountered:
Hello @artempyanykh and thanks for using Farkle! I am very glad it serves you well.
Error recovery is indeed a gap in Farkle's feature set and unfortunately something I will not work at any time soon. My time is pretty limited these days and I have lots of other things in mind for Farkle. But I acknowledge that this is an important feature to have.
If you have any ideas on the user-facing APIs to implement error handling, I will be glad to hear them.
Hey @teo-tsirpanis, that's all right! Farkle as-is is already very-very helpful, much more so than fslexyacc was for me. Thanks for putting in the hard work.
For now, I can probably go by without finer error recovery, but if things change I'll make sure to follow up here.
I've started using Farkle to build a parser for a programming language. I'm happy with the library and the results I'm getting, so thanks for working on it!
One thing that's not very clear to me is how to do error recovery with Farkle – with parser generators a-la yacc/bison/menhir I have access to 'error' productions; by inserting it in strategic places I can make the parser parse as much as possible while accumulating parse errors. Is there a similar mechanism in Farkle?
The text was updated successfully, but these errors were encountered: