Adding Rust parser
OpenAnt currently supports Go, Python, JS/TS(beta), C/C++(beta), PHP(beta), Ruby(beta) only.
- However, I want to try this tool with repositories that contain
rust-crates &/or other Rust components.
- I'll maybe even submit some PRs soon if not later; but I'd love to hear what the maintainers think.
Hence, I'm also looping in @ar7casper since they've worked on most other parsers & language support, if not all. So I'd love to especially hear what you think.
Goal:
➜ Add a Rust parser so repos containing Rust crates can run:
- " $
openant init < ... > -l rust", &
- " $
openant parse", successfully.
Open Questions:
- Which approach best matches OpenAnt’s parser architecture:
tree-sitter-rust, rust-analyzer, or another AST strategy?
- Are there any must-have outputs/IR fields the Rust parser needs to populate for later stages ( enhancements / analysis / verification )?
- How this maps against your current plans; &
- If you've got other conflicting considerations &/or blockers that I may be unaware of.
Hence, if this sounds good, I could perhaps try & submit a minimal Rust fixture & parser, etc.
( ...especially if it's not on your immediate agenda. Lmk.)
Example personal repo;
( that I'd love to assess using OpenAnt )
Adding Rust parser
OpenAnt currently supports
Go,Python,JS/TS(beta),C/C++(beta),PHP(beta),Ruby(beta) only.Goal:➜ Add a
Rustparser so repos containing Rust crates can run:openant init < ... > -l rust", &openant parse", successfully.Open Questions:
Example personal repo;