宣布Clippy功能冻结

宣布Clippy功能冻结
Announcing the Clippy feature freeze

原始链接: https://blog.rust-lang.org/inside-rust/2025/06/21/announcing-the-clippy-feature-freeze/

Clippy 将从 2025 年 6 月 26 日（Rust 1.89.0 beta 版）到 2025 年 9 月 18 日（Rust 1.89.0 正式版）进行为期 12 周的功能冻结。在此期间，将不接受任何新功能（lint），重点放在错误修复和改进现有 lint 的准确性上。用户可以期待更少的误报和更好的边缘情况处理。新的 lint 建议仍然欢迎以 issue 的形式提交，但相关的 pull request 将在冻结期后审核。高级的新 lint PR 可能会根据具体情况进行审核。用户可以通过报告错误、处理现有 issue、改进文档或修复崩溃来提供帮助。目标是提高现有 lint 的质量和可维护性。可以通过贡献指南、“good first issues”、Zulip 和用于反馈的草稿 pull request 获得帮助。此暂停旨在确保 Clippy 的长期健康，并为 Rust 用户提供更高质量的体验。

The Rust programming language's "Clippy," a static analysis tool that catches common coding mistakes and suggests improvements, is entering a feature freeze. Clippy allows customization of rules to fit project needs, like prohibiting shadowing or addressing potential panic scenarios. A commenter questioned why Clippy isn't integrated within the Rust compiler given its complexity. Another user responded that Clippy is built and tested during Rust compiler CI, but its large and growing collection of lints warrant occasional freezes for codebase maintenance. Several people have contributed to Clippy, highlighting its value as a learning resource for understanding how the Rust compiler interprets code, from abstract syntax trees to type checking. Finally, a user asked if there's a Clippy lint to detect filling and immediately clearing a collection. The post was also clarified as unrelated to Microsoft Clippy.

The Clippy project will be on feature-freeze for 12 weeks, starting from Rust 1.89.0 beta (June 26th 2025) to September 18th 2025 (Rust 1.89.0 stable release). During this time no new features will be accepted, only bug fixes.

This feature freeze comes from a lack of the necessary capacity needed to maintain all the current lints (over 750 of them 😱) and still add new ones. We need to care for the Clippy project the same way that Clippy cares about our code, and note that every single one of them needs maintaining and accounting for current and future changes in the compiler as a whole.

As a team we’ll focus on making contributing the best it can be, and mark the issues that could be great as a starting point to get familiar with the project.

As a user you can expect to have more accurate lints, with less false positives and more edge cases covered. A bump into Clippy’s toolchain would not involve the same risk for false positives as it has been until now. We hope that by upping the standard for lints all around the project we can allow users to expect even more from the already great linter.

If you have a lint which you want to be implemented, you can still open an issue for it, but PRs adding new lints won't be reviewed during the feature freeze. Instead, they will be put into a queue and reviewed (and merged) after the feature freeze is over.

Open pull requests that add new lints and are in a very advanced state might still get reviewed and/or merged during the feature freeze.

our contributing guidelines and check our suggested good first issues for opening pull requests. Everything from fixing diagnostic issues and improving documentation, to fixing application-wide crashes really helps Clippy get into the excellent state that our users deserve.

If you need direct help when fixing a bug, don't hesitate to open a thread on Zulip and/or open a draft PR with the questions you have in order to start the feedback stream.

宣布Clippy功能冻结 Announcing the Clippy feature freeze

What can I expect as a user?

Can I help?

Conclusion

宣布Clippy功能冻结
Announcing the Clippy feature freeze