-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is holding this back? #2
Comments
It's hard to answer. General issues would include the lack of many examples, practicality, and maturity. But they may only be addressed by long-term, continuous development. Regarding practicality, I personally think some existing approaches, including ours, have (certain) potential, but at least I haven't made enough effort to make this potential evident to users. Being more technical, parsing/printing is not that symmetric due to control over prettiness (of printing) and lexers. So, to make the system practical, we need to address these things to some extent by certain means. Also, if we want to use some parsing methods that can handle left recursions, we may need to make recursive definitions explicit so that the system can handle them, which would introduce another issue. Haskell does not allow us to change the meaning of recursive definitions, except for value recursions for monads ( |
Are you using flippre regularly? For asymmetry of printing I have added Reader and State to the printer monad and ensure that the parser can handle all the variations. |
To be honest, no. One reason is that there is not so much opportunity to write parsers/printers, especially because I recently focused on embedded DSLs.
Sounds interesting. Where can I find out in the repo how these monads are used in printing? |
An example of it in use https://github.com/BebeSparkelSparkel/biparsing/blob/0f60850822a0dfd6c11afc5804c957fcb15511c6/examples/WriterState.hs#L80 Currently doing a lot of house keeping but right now it is in An instance of BackwardC https://github.com/BebeSparkelSparkel/biparsing/blob/c9b15449ad8fff4f873b26b03b015a9c158f33a8/biparsing-mixes/src/Prelude.hs#L54 |
Thank you. I will take a look. Sorry for the late reply. |
Thanks for the reference.
Seems like there is a fair amount of interest in this area but no implementation has had any traction.
What in your opinion is holding bidirectional programming, specifically parsing and printing, from being usable?
The text was updated successfully, but these errors were encountered: