惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
G
Google Developers Blog
Blog — PlanetScale
Blog — PlanetScale
U
Unit 42
A
About on SuperTechFans
Vercel News
Vercel News
B
Blog
Martin Fowler
Martin Fowler
MyScale Blog
MyScale Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
腾讯CDC
D
Docker
V
Visual Studio Blog
博客园 - 叶小钗
The Cloudflare Blog
Jina AI
Jina AI
B
Blog RSS Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
WordPress大学
WordPress大学
T
Tailwind CSS Blog
MongoDB | Blog
MongoDB | Blog
D
DataBreaches.Net
月光博客
月光博客
大猫的无限游戏
大猫的无限游戏

Rust Blog

Security Advisory for Cargo (CVE-2026-5223) | Rust Blog Security Advisory for Cargo (CVE-2026-5222) | Rust Blog Project goals update — April 2026 (end of 2025H2) | Rust Blog Rust is participating in Outreachy | Rust Blog Raising the baseline for the `nvptx64-nvidia-cuda` target | Rust Blog Announcing Google Summer of Code 2026 selected projects | Rust Blog Announcing Rust 1.95.0 | Rust Blog docs.rs: building fewer targets by default | Rust Blog Changes to WebAssembly targets and handling undefined symbols | Rust Blog Announcing Rust 1.94.1 | Rust Blog Security advisory for Cargo | Rust Blog What we heard about Rust's challenges | Rust Blog Call for Testing: Build Dir Layout v2 | Rust Blog Announcing rustup 1.29.0 | Rust Blog Announcing Rust 1.94.0 | Rust Blog 2025 State of Rust Survey Results | Rust Blog Rust debugging survey 2026 | Rust Blog Update on the October 15, 2018 incident on crates.io Announcing Rust 1.29.2 Announcing Rust 1.29 Announcing Rust 1.28 What is Rust 2018? Announcing Rust 1.27.2 Announcing Rust 1.27.1 Security Advisory for rustdoc Announcing Rust 1.27 Announcing Rust 1.26.2 Announcing Rust 1.26.1 Rust turns three Announcing Rust 1.26
Announcing the Clippy feature freeze | Inside Rust Blog
blyxyas on behalf of the Clippy team · 2025-06-21 · via Rust Blog

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.

What can I expect as a user?

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.

Can I help?

As always, any help on the project is very appreciated. Apart from opening bug reports, you can follow 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.

Conclusion

Thanks a lot for all these years of supporting Clippy, we hope that via this little feature hiatus we can achieve the excellence that the Rust user base deserves.