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

ENH: convert syntax tree to JSON #49

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

johnyf
Copy link
Contributor

@johnyf johnyf commented Sep 28, 2021

These changes serialize the abstract syntax tree as JSON.

@johnyf johnyf force-pushed the json_of_syntax_tree branch 2 times, most recently from a1809e5 to a925df1 Compare September 29, 2021 14:24
- API: add command-line option `--json-ast`
@johnyf johnyf force-pushed the json_of_syntax_tree branch from a925df1 to 75f1674 Compare October 29, 2021 12:53
@ahelwer
Copy link
Collaborator

ahelwer commented Dec 4, 2024

@johnyf do you think something like this would be better implemented by sticking PPX macros onto our data structures?

@johnyf
Copy link
Contributor Author

johnyf commented Dec 5, 2024

Not sure about PPXs. It may be simpler to have an implementation as a function.

@ahelwer
Copy link
Collaborator

ahelwer commented Dec 5, 2024

This seems like useful functionality I'd like to play around with, would you be able to rebase and fix the conflicts?

P.S. what does ENH stand for?

@johnyf
Copy link
Contributor Author

johnyf commented Dec 6, 2024

I will try to rebase the changes. The prefix "ENH" stands for "enhancement" (in the sense of a new feature), and is among acronyms listed in numpy's documentation https://numpy.org/doc/stable/dev/development_workflow.html#writing-the-commit-message.

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

Successfully merging this pull request may close these issues.

2 participants