rust-lang / rust-lang/rust-playground
Support "Backtrace" setting for Clippy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
The "Backtrace" setting is currently ignored when executing Clippy. It would be nice if this could be supported.
Note for testing: In Clippy we have an internal lint which is designed to produce ICEs called clippy::produce_ice. However, this one is hidden behind a feature gate. I think we could enable it on nightly for some time if that helps with development. Otherwise, we might be able to find a "simple" ICE on stable that would at least be valid for some time 🙃
Another tiny improvement for tools would also be to adjust the node inside the output with the text "note: run with RUST_BACKTRACE=1 environment variable to display a backtrace" to rerun the actual tool, currently it starts the normal build.
Related: #545
Thank you for the work, the playground is a really nice and important tool! 👍
Contributor guide
No contributing guide indexed for this repository
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 by tracing how the Playground executes Clippy and how the Backtrace setting is handled. Use the hidden clippy::produce_ice lint on nightly, if available, to verify behavior; done means Backtrace controls the Clippy run and the output note reruns Clippy rather than a normal build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100