rust-lang / rust-lang/rust-analyzer
add fuzzing target for making sure proc-macro fixup's output can be parsed with syn
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
To avoid unnecessarily causing proc-macros to error, the fixup code should not produce output that can't be parsed with syn. So, I think we should add a fuzzing target for generating arbitrary input tokens and/or AST, passing that into the proc-macro input fixup code, and erroring if the tokens passed into the proc-macro can't be parsed with syn.
Originally mentioned: #t-compiler/rust-analyzer > splitting out parser for use as an alternative to syn @ 💬
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proc-macro input fixup code and determine how arbitrary input tokens or ASTs can be passed through it. Add a fuzzing target that reports failure when the resulting proc-macro tokens cannot be parsed with syn. Done means malformed output is detected by the fuzz target without unnecessarily causing proc-macros to error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100