-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Allow block definitions in if/for/match blocks (fixes #335) #336
Conversation
@jmafc do you want to try this out? |
Do I just have to reference the master branch in my Cargo.toml to do that? |
Well, the |
Ok, I tried it, but it still causes the message: |
Ah yes, I forgot to strip out the code in the code generator that panics if it encounters a nested block definition. That's fixed with the latest push. Can you file a separate issue about the macro thing? That seems unrelated, and potentially a regression. Would like have a minimal reproduction of the template syntax for that. |
Ok, the |
And does the template with the if-nested block produce the expected output? :) |
Yes it did produce the expected output (eventually, because one of my templates had an unrecognized field, but I've fixed that now). |
Cool, thanks for checking. |
No description provided.