experiencing rust code so good I have to cargo doc to find out what fields an unnameable type has. rustc calls it InnerBehaviourEvent, but that's not it. I can't see a way to instrument rustc to dump me the type so I'm hoping cargo doc can see it at least 🥴
November 16, 2025 at 9:18 PM
experiencing rust code so good I have to cargo doc to find out what fields an unnameable type has. rustc calls it InnerBehaviourEvent, but that's not it. I can't see a way to instrument rustc to dump me the type so I'm hoping cargo doc can see it at least 🥴
🦀 This Week in Rust #625!
Highlights:
→ LLVM RealtimeSanitizer lands in rustc
→ Google's Magika 1.0 rebuilt in Rust (1K files/sec!)
→ Automesh: mesh generation 1000x faster
→ SeaORM 2.0 type improvements
Deep dive: tinyurl.com/ywkd6uk6
#rustlang #programming
Highlights:
→ LLVM RealtimeSanitizer lands in rustc
→ Google's Magika 1.0 rebuilt in Rust (1K files/sec!)
→ Automesh: mesh generation 1000x faster
→ SeaORM 2.0 type improvements
Deep dive: tinyurl.com/ywkd6uk6
#rustlang #programming
This Week in Rust #625: Safety Tools, Mesh Generation & Type-Safe ORMs
Hey Rustaceans!
tinyurl.com
November 16, 2025 at 3:36 PM
🦀 This Week in Rust #625!
Highlights:
→ LLVM RealtimeSanitizer lands in rustc
→ Google's Magika 1.0 rebuilt in Rust (1K files/sec!)
→ Automesh: mesh generation 1000x faster
→ SeaORM 2.0 type improvements
Deep dive: tinyurl.com/ywkd6uk6
#rustlang #programming
Highlights:
→ LLVM RealtimeSanitizer lands in rustc
→ Google's Magika 1.0 rebuilt in Rust (1K files/sec!)
→ Automesh: mesh generation 1000x faster
→ SeaORM 2.0 type improvements
Deep dive: tinyurl.com/ywkd6uk6
#rustlang #programming
actually rustc ICEs on just
let _: bool = dbg!(&0) < 0;
:)
let _: bool = dbg!(&0) < 0;
:)
November 16, 2025 at 7:17 AM
actually rustc ICEs on just
let _: bool = dbg!(&0) < 0;
:)
let _: bool = dbg!(&0) < 0;
:)
what on earth are you doing to get this long of build times???
in my experience building all of rustc takes like maybe 5-10 minutes.
in my experience building all of rustc takes like maybe 5-10 minutes.
November 15, 2025 at 6:22 PM
what on earth are you doing to get this long of build times???
in my experience building all of rustc takes like maybe 5-10 minutes.
in my experience building all of rustc takes like maybe 5-10 minutes.
Interesting that according to https://fex-emu.com/FEX-2510/ , since 2019, MSVC has been emitting metadata for aiding x86 emulation on aarch64 to indicate regions of code where TSO doesn’t matter.
Does LLVM as used in clang-cl and rustc do this?
Does LLVM as used in clang-cl and rustc do this?
FEX 2510 Tagged
We’re just gonna kick out this little release and be on our way. There might be some interesting things this month, read and find out!
fex-emu.com
November 14, 2025 at 6:25 PM
Interesting that according to https://fex-emu.com/FEX-2510/ , since 2019, MSVC has been emitting metadata for aiding x86 emulation on aarch64 to indicate regions of code where TSO doesn’t matter.
Does LLVM as used in clang-cl and rustc do this?
Does LLVM as used in clang-cl and rustc do this?
The only limitation at the moment is in rustc/llvm/linker. Unfortunately the only workaround I've found forces us to marginally bloat the binary size. It has no runtime impact but it's still annoying. My attempt to modify rustc caused crazy link errors so I gave up 😅
November 14, 2025 at 1:18 PM
The only limitation at the moment is in rustc/llvm/linker. Unfortunately the only workaround I've found forces us to marginally bloat the binary size. It has no runtime impact but it's still annoying. My attempt to modify rustc caused crazy link errors so I gave up 😅
Some of this is due to rustc issues - needs better distributable formats for shared libs and system libs, features + whole program optimization make sharing difficult
But cargo itself sucks at just, like, being able to specify an out directory
But cargo itself sucks at just, like, being able to specify an out directory
November 14, 2025 at 10:14 AM
Some of this is due to rustc issues - needs better distributable formats for shared libs and system libs, features + whole program optimization make sharing difficult
But cargo itself sucks at just, like, being able to specify an out directory
But cargo itself sucks at just, like, being able to specify an out directory
Sorry that I don't have the confidence to contribute to rustc
November 14, 2025 at 9:16 AM
Sorry that I don't have the confidence to contribute to rustc
Sur arch Intel, un ptit 'apt install rustc cargo' et le problème est réglé. Le vrai point noir, c'est toutes les archs non supportées par Rust qui vont devoir "disparaitre" dans Debian :(
November 12, 2025 at 2:55 PM
Sur arch Intel, un ptit 'apt install rustc cargo' et le problème est réglé. Le vrai point noir, c'est toutes les archs non supportées par Rust qui vont devoir "disparaitre" dans Debian :(
Added a new rustc lint which will hopefully prevent a lot of very wrong casts: `function_casts_as_integer`.
In short, if you convert a function to an integer, it will now warn.
Why? Because of cases like:
```rust
let _ = [0; u8::max as usize];
```
1/2
In short, if you convert a function to an integer, it will now warn.
Why? Because of cases like:
```rust
let _ = [0; u8::max as usize];
```
1/2
Add new `function_casts_as_integer` lint by GuillaumeGomez · Pull Request #141470 · rust-lang/rust
The function_casts_as_integer lint detects cases where users cast a function pointer into an integer.
warn-by-default
Example
fn foo() {}
let x = foo as usize;
warning: casting a function into an i...
github.com
November 11, 2025 at 4:52 PM
Added a new rustc lint which will hopefully prevent a lot of very wrong casts: `function_casts_as_integer`.
In short, if you convert a function to an integer, it will now warn.
Why? Because of cases like:
```rust
let _ = [0; u8::max as usize];
```
1/2
In short, if you convert a function to an integer, it will now warn.
Why? Because of cases like:
```rust
let _ = [0; u8::max as usize];
```
1/2
What am I doing wrong? Is this lint gone in a more recent version of rust?
13:58:53 me@silverplate:src$ rustc --version
rustc 1.89.0 (29483883e 2025-08-04) (gentoo)
2 | #![deny(integer_to_ptr_transmutes)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(unknown_lints)]` on by default
13:58:53 me@silverplate:src$ rustc --version
rustc 1.89.0 (29483883e 2025-08-04) (gentoo)
2 | #![deny(integer_to_ptr_transmutes)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(unknown_lints)]` on by default
November 10, 2025 at 2:00 PM
What am I doing wrong? Is this lint gone in a more recent version of rust?
13:58:53 me@silverplate:src$ rustc --version
rustc 1.89.0 (29483883e 2025-08-04) (gentoo)
2 | #![deny(integer_to_ptr_transmutes)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(unknown_lints)]` on by default
13:58:53 me@silverplate:src$ rustc --version
rustc 1.89.0 (29483883e 2025-08-04) (gentoo)
2 | #![deny(integer_to_ptr_transmutes)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(unknown_lints)]` on by default
November 9, 2025 at 11:34 PM
in honour of yet another rustc dev coming out as trans, i propose that we rename Compiler Diagnostics to Compiler Dysphorias
November 9, 2025 at 12:55 PM
in honour of yet another rustc dev coming out as trans, i propose that we rename Compiler Diagnostics to Compiler Dysphorias
they also pretend that other compilers are immune to bugs. no, they definitely aren't. llvm and the gcc break stuff regularly, just like rustc lol
November 8, 2025 at 9:56 PM
they also pretend that other compilers are immune to bugs. no, they definitely aren't. llvm and the gcc break stuff regularly, just like rustc lol
the speaker doesn't understand how rustc is released and distributed on Debian derivatives, and their criticisms are easily summarized as: "rewrites can change behavior"
like... yeah, obviously.
the same problems have came from refactors in C, except you also deal with memory safety/libc nonsense
like... yeah, obviously.
the same problems have came from refactors in C, except you also deal with memory safety/libc nonsense
November 8, 2025 at 9:56 PM
the speaker doesn't understand how rustc is released and distributed on Debian derivatives, and their criticisms are easily summarized as: "rewrites can change behavior"
like... yeah, obviously.
the same problems have came from refactors in C, except you also deal with memory safety/libc nonsense
like... yeah, obviously.
the same problems have came from refactors in C, except you also deal with memory safety/libc nonsense
WebAssembly ランタイムの wasmtime が Rust で書かれてて、そのバックエンドが cranelift と呼ばれているんだけど、rustc のバックエンドとして LLVM の代わりに cranelift を使うことができたはずで、コード生成が速くなったりしないか？
November 8, 2025 at 8:56 AM
WebAssembly ランタイムの wasmtime が Rust で書かれてて、そのバックエンドが cranelift と呼ばれているんだけど、rustc のバックエンドとして LLVM の代わりに cranelift を使うことができたはずで、コード生成が速くなったりしないか？
I more strongly associate rustc with the specific binary `rustc`, compared to rustdoc which as far as I'm concerned could be a library with a different name. Maybe this explains why I care more about case for the former?
November 6, 2025 at 3:59 AM
I more strongly associate rustc with the specific binary `rustc`, compared to rustdoc which as far as I'm concerned could be a library with a different name. Maybe this explains why I care more about case for the former?
observation: Rustdoc as the start of a sentence seems fine. Rustc on the other hand seems viscerally wrong. rustc is the only way to capitalize that. rustdoc is also acceptable here, but not required.
November 5, 2025 at 8:31 PM
observation: Rustdoc as the start of a sentence seems fine. Rustc on the other hand seems viscerally wrong. rustc is the only way to capitalize that. rustdoc is also acceptable here, but not required.
Stumbled upon this great tutorial for C/C++ devs who want to port highly parallel code to Rust.
Shows OpenMP -> Rayon migration, tricks for instruction level parallelism, SIMD, compares assembly and performance of gcc/clang/rustc generated code, and overall explains the concepts very well.
Shows OpenMP -> Rayon migration, tricks for instruction level parallelism, SIMD, compares assembly and performance of gcc/clang/rustc generated code, and overall explains the concepts very well.
Introduction - Comparing parallel Rust and C++
parallel-rust-cpp.github.io
November 5, 2025 at 11:42 AM
Stumbled upon this great tutorial for C/C++ devs who want to port highly parallel code to Rust.
Shows OpenMP -> Rayon migration, tricks for instruction level parallelism, SIMD, compares assembly and performance of gcc/clang/rustc generated code, and overall explains the concepts very well.
Shows OpenMP -> Rayon migration, tricks for instruction level parallelism, SIMD, compares assembly and performance of gcc/clang/rustc generated code, and overall explains the concepts very well.
Sincerely considering moving my day to day eng work off of the usual company macbook to a Linux workstation so I can fan out rustc over all the homelab cores I have lying around....
November 5, 2025 at 4:49 AM
Sincerely considering moving my day to day eng work off of the usual company macbook to a Linux workstation so I can fan out rustc over all the homelab cores I have lying around....
in a Rust/tokio discord channel, today's part as a notepad screenshot because characters:
Alper — Yesterday at 22:15
Claude spit out a dozen or so files that are supposed to be an ansible deployment. So that's straight-forward enough.
Alper — Yesterday at 22:15
Claude spit out a dozen or so files that are supposed to be an ansible deployment. So that's straight-forward enough.
November 4, 2025 at 4:14 PM
in a Rust/tokio discord channel, today's part as a notepad screenshot because characters:
Alper — Yesterday at 22:15
Claude spit out a dozen or so files that are supposed to be an ansible deployment. So that's straight-forward enough.
Alper — Yesterday at 22:15
Claude spit out a dozen or so files that are supposed to be an ansible deployment. So that's straight-forward enough.
This is casting an immutable reference to a mutable one. This breaks all of rust‘s safety guarantees. rustc will make optimizations on the assumption that such casts don’t happen
November 2, 2025 at 9:02 PM
This is casting an immutable reference to a mutable one. This breaks all of rust‘s safety guarantees. rustc will make optimizations on the assumption that such casts don’t happen
A bunch of people are mad Debian is requiring rustc to work, and therefore dropping support for old architectures. The architectures in question:
- DEC Alpha (1992-2007)
- PA-RISC (1986-2008)
- Motorola 68000 (1979-1994)
- Hitachi SuperH (this is the only one that still seems in [very niche] use)
- DEC Alpha (1992-2007)
- PA-RISC (1986-2008)
- Motorola 68000 (1979-1994)
- Hitachi SuperH (this is the only one that still seems in [very niche] use)
November 2, 2025 at 7:58 PM
A bunch of people are mad Debian is requiring rustc to work, and therefore dropping support for old architectures. The architectures in question:
- DEC Alpha (1992-2007)
- PA-RISC (1986-2008)
- Motorola 68000 (1979-1994)
- Hitachi SuperH (this is the only one that still seems in [very niche] use)
- DEC Alpha (1992-2007)
- PA-RISC (1986-2008)
- Motorola 68000 (1979-1994)
- Hitachi SuperH (this is the only one that still seems in [very niche] use)
#rustlang now supports tier1 windows arm 64 processors using the aarch64-pc-windows-msvc build target with the release of 1.91.0 doc.rust-lang.org/rustc/platfo...
Platform Support - The rustc book
doc.rust-lang.org
November 2, 2025 at 11:07 AM
#rustlang now supports tier1 windows arm 64 processors using the aarch64-pc-windows-msvc build target with the release of 1.91.0 doc.rust-lang.org/rustc/platfo...
hard dependency on rustc for apt so that they can parse input in a way that isn't the software equivalent of clipping jumper cables directly to overhead lines
November 2, 2025 at 1:55 AM
hard dependency on rustc for apt so that they can parse input in a way that isn't the software equivalent of clipping jumper cables directly to overhead lines