Skip to content

Expose prettyprint/serialize/parse options in rust #3463

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

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

Conversation

segiddins
Copy link
Contributor

No description provided.

@segiddins segiddins force-pushed the segiddins/expose-prettyprint-serialize-parse-options-in-rust branch from ffece4f to 23fe580 Compare February 13, 2025 23:44
@segiddins segiddins force-pushed the segiddins/expose-prettyprint-serialize-parse-options-in-rust branch from 23fe580 to 0a0f2c2 Compare February 14, 2025 00:02
@kddnewton
Copy link
Collaborator

I'm okay with prettyprint and the parse options, but I'm not sure I understand the use case for the serialization API in rust. Could you explain the motivation?

@segiddins
Copy link
Contributor Author

The motivation is the ability to parse the AST into a more natural shape for use in rust, similar to what the prism ruby gem does (rather than maintaining pointers to the c structure nodes). I am using it in https://github.com/segiddins/gemfile-rs/blob/main/src/prism_ast/generated.rs, an in-progress project of mine

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 this pull request may close these issues.

2 participants