Skip to content

Commit 0e0a95d

Browse files
focus on clippy only
1 parent 4cfe55a commit 0e0a95d

File tree

1 file changed

+6
-13
lines changed

1 file changed

+6
-13
lines changed

posts/2021-05-06-Rust-1.52.0.md

+6-13
Original file line numberDiff line numberDiff line change
@@ -25,20 +25,13 @@ from the appropriate page on our website, and check out the
2525

2626
## What's in 1.52.0 stable
2727

28-
This release is fairly small, primarily containing stabilizations of various APIs in the standard library.
28+
The most significant change in this release is not to the language or standard
29+
libraries, but rather an enhancement to tooling support for Clippy.
2930

30-
We have also closed out a long-standing [bug] in the Rust compiler. Previously, LLVM assumed that the program would make progress, and used this to optimize. This meant that certain constructs in safe Rust were removed or otherwise miscompiled, such as infinite loops (`loop {}`) or recursion which didn't terminate.
31-
32-
In Rust 1.49.0, we landed a [partial fix] to this bug specifically targeting
33-
`loop {}`, but this fix brings an LLVM upgrade which avoids needing workarounds
34-
for these cases, fixing the larger class of bug.
35-
36-
Clippy has also gained a significant usability improvement: it no longer shares
37-
its build cache with `cargo check`, which means that errors and warnings will be
38-
properly reported when running it after `cargo check`.
39-
40-
[bug]: https://github.com/rust-lang/rust/issues/28728
41-
[partial fix]: https://github.com/rust-lang/rust/pull/77972
31+
Previously, running `cargo check` followed by `cargo clippy` wouldn't actually
32+
run clippy: the build caching in Cargo didn't differentiate between the two. In
33+
1.52, however, this has been fixed, which means that users will get the expected
34+
behavior independent of the order in which they run the two commands.
4235

4336
### Stabilized APIs
4437

0 commit comments

Comments
 (0)