-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Proc -> NoReturn with controlled recursion #2284
Comments
Or any better idea how to handle this recursion/lazyness? 💃 |
Hi, Just like in #2283, if you don't provide code that we can copy and paste to immediately reproduce the problem you are having, so we can debug and fix the bug, there's not much we can do. |
Oh, sorry, I see you provided a link to the github repo. That's good. In any case, it's better if you try to reduce the code to the minimum that exhibits the problem. |
Hmmm... Just ran |
@asterite I just created another sample which uses recursive parser. could you please try to run it. https://github.com/umurgdk/haydari/blob/master/samples/brainfuck_recursive.cr#L85
|
Ping. |
Please also try to provide reduced code that reproduces this. The problem with links to repos is that they eventually change and then the issue becomes harder to reproduce. |
Two weeks afterwards, I'm closing this. Please reopen if you have reproducible code for this. Thanks! |
Hi im working on a parser combinator library and i have small issues with proc return types. To be able to handle recursion for parsers i have to make it lazy, to be able to do it I have a ParserClosure class which accepts a proc to be ran when it is needed. You can see see the codes below.
In case of you want to see all the codes please check https://github.com/umurgdk/haydari
This code doesn't work also for another issue about
parse_program
's return type. Please see #2283The text was updated successfully, but these errors were encountered: