On 11/17/25 1:02 PM, Miguel Ojeda wrote:
On Mon, Nov 17, 2025 at 9:07 AM Miguel Ojeda ojeda@kernel.org wrote:
Examples (i.e. doctests) may want to use names such as `foo`, thus the `clippy::disallowed_names` lint gets in the way.
Thus allow it for all doctests.
In addition, remove it from the existing `expect`s we have in a few doctests.
This does not mean that we should stop trying to find good names for our examples, though.
Suggested-by: Alice Ryhl aliceryhl@google.com Link: https://lore.kernel.org/rust-for-linux/aRHSLChi5HYXW4-9@google.com/ Signed-off-by: Miguel Ojeda ojeda@kernel.org
Applied to `rust-next` -- thanks everyone!
Is rust-next a rebasing branch? I was going to request a non-empty commit body, in order to make it more immediately clear what this does. Something like:
The current set of disallowed names is inherited from clippy's defaults [1], which are "foo", "baz", and "quux". This may be extended via .clipy.toml, which so far has no entries for disallowed names.
thanks,