Skip to content

Address September PM blog feedback #1719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 15, 2025
Merged

Address September PM blog feedback #1719

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
26fd6d8
Give credit to Tathagata Roy on the Coccinelle for Rust session
tomassedovic Oct 15, 2025
c358cbe
Address feedback by Pierre-Emmanuel Patry
tomassedovic Oct 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/inside-rust/program-management-update-2025-09.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,8 @@ info!("Window resized to: {width}x{height}");

across the codebase. Across all such `format!`-like invocations, parameters etc. And taking care to not interpolate field accesses or function calls (which are currently not allowed in the "format strings").

Tathagata Roy ran the workshop for us. We tested Coccinelle out on some pre-existing examples, including the one above. The evening after, I ran it on all my repos. I'm really excited about this.

**Clippy**

There was a really good status update on Clippy work specifically for Rust for Linux by Alejandra González. I had no idea that was happening, but it makes perfect sense. Clippy can highlight code that's not desirable even if it's allowed by the Rust compiler.
Expand Down Expand Up @@ -131,15 +133,15 @@ The "front-end" here means that GCCRS reads Rust code and transforms it into an

[ir]: https://en.wikipedia.org/wiki/Intermediate_representation

Pierre highlighted the difficulties of compiling even a "simple" `for` loop: to do that you need to be able to resolve traits and handle iterators and macros.
Pierre-Emmanuel highlighted the difficulties of compiling even a "simple" `for` loop: to do that you need to be able to resolve traits and handle iterators and macros.

Their main target is to compile Rust's [core library][core].

[core]: https://doc.rust-lang.org/core/

After that, they've set their sights on compiling the Linux kernel (including the Rust part). Linux can currently be built with either GCC or LLVM, but it is strongly recommended that everything use one or the other. This will be beneficial to some projects that are required to use the GCC toolchain.

Interestingly, the project is completely ignoring a borrow checker for now. Instead, their goal is to compile *correct* Rust programs — i.e. only those that `rustc` itself would compile. In the future, they plan to look into [Polonius][polonius], but it would be premature at this point.
Interestingly, the main effort is not going into the borrow-checker at all. They're using [Polonius][polonius] right now and the compiler is only handling *correct* Rust programs. In the future they're looking to integrate the next-gen borrow checker, but that's some ways off (and would require it being moved to its own crate).

[polonius]: https://github.com/rust-lang/polonius

Expand Down