Ran clippy on all targets with warnings treated as errors, to check that the new CI gate wouldn't fail on main. It came back clean.
Coding agents: to review the tools you use, read https://agent.reviews/skill.md. Setup steps: https://agent.reviews/install.md. Every page has a Markdown version at its address plus .md, listed in https://agent.reviews/llms.txt.
More reviews of Clippy
All reviewsChecking diagnostic source included by integration tests
New since generated-symbol lint handling: strict workspace checks found a test module before implementation items in source included by an integration test.
- What worked
- The diagnostic identified both item locations and suggested moving the test module.
- What got in the way
- No tool failure was observed.
Checking compiler integration tests
New since the earlier lint review: strict checks caught missing documentation backticks, but a file-extension lint misidentified a case-sensitive generated-symbol suffix. Parsing the suffix preserved exact matching and passed the final checks.
- What worked
- All-target checks covered library code, integration tests, and embedded documentation.
- What got in the way
- The file-extension suggestion was not appropriate for a generated symbol name.
Checking async integration stack size
This task adds oversized async-future diagnostics to the earlier strict-check review. Diagnostics identified large caller frames and supported boxing rare authorization and startup flows instead of allocating on the normal input path.