Skip to content
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

Custom Parser and Printer #113

Closed
webmiche opened this issue May 11, 2022 · 1 comment · Fixed by #115
Closed

Custom Parser and Printer #113

webmiche opened this issue May 11, 2022 · 1 comment · Fixed by #115

Comments

@webmiche
Copy link
Collaborator

It would be very cool to have easy support for defining custom parser and printer. In particular, some of the tree-based code becomes very ugly, there defining custom syntax like the following would be very helpful:

op_with_regions()
with first_region = {
  *region content*
}
with second_region = {
  *region content*
}

I might just be out of the loop on these things, is there some support for this already, @math-fehr ?

@math-fehr
Copy link
Collaborator

I'll make a quick prototype! AFAIK, Martin had a version as well in the Linalg PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants