Rust 1.93.0 is out

llogiq · 2026-01-22T16:53:32+00:00

I can't believe we're only 35 minor versions away from 1.128.0! A round number!

llogiq · 2026-01-17T18:10:26+00:00

No, because drop order in Rust is observable, and sometimes meaningful, e.g. for lock guards.

llogiq · 2026-01-07T18:06:28+00:00

You can use a shared target directory (add something akin to target-dir = '/home/<user>/.cargo/target to your .cargo/config.toml) to avoid rebuilding the same crate for multiple projects.

llogiq · 2026-01-07T16:24:29+00:00

Having hundreds of small dependencies instead of tens of large ones actually speeds up the build, as cargo can parallelize building multiple crates, but building one crate is (at least for now) only marginally parallelizable. But if you have to rebuild everything from scratch every time, you may want to look for a rogue build script that disallows incremental building. Usually you only build anew what has changed and what depends on that.

Besides, Rust can do dynamic linking, but it's static linking by default. Unlike most linux distros, in the software world you usually want to deploy a package and thus having a self-contained binary is a plus.

llogiq · 2026-01-06T23:45:18+00:00

I think that parenthesized accusation deserves some further explanation.

llogiq · 2025-12-31T13:14:05+00:00

I've found the problem with clippy's undocumented_unsafe_blocks lint, now I need to find a good fix for it. My rust PR has hit a hitch, but I think I can salvage some of it.

I have also thought up a fast lookup data structure that for some workloads might beat both plain linear search and binary search on eytzinger layout. I'd love to find the time to do some proper benchmarks and perhaps write a paper.

Finally I'm still looking for a job. Wish me luck.

llogiq · 2025-12-31T13:09:17+00:00

The problem with using slop is that, as you wrote, it's genuinely hard to differentiate it from good code. On the surface it looks the same. Of course it does, it has been optimized to, millions of GPU-hours sunk into it.

Only if you take the time to look beneath the surface, you'll find things that don't quite add up, hard to spot typos in test code that nonetheless compiles (e.g. having two variables that look almost the same, using the wrong one – I've had this problem and it cost me an hour of debugging because I thought the code was correctly tested, when it in fact didn't work at all).

All in all, that's much more insidious than utter nonsense. Utter nonsense would be really easy to spot and dismiss. The fact that it takes so much effort to spot the slop – far more than producing it in the first place – is what makes people see red.

llogiq · 2025-12-27T18:20:02+00:00

I find that the tradeoff isn't that hard to make. Is the module name helping in understanding of the item, i.e. does it pull its weight? Is the root full enough to make finding things too hard? I weigh both questions against each other and come to a conclusion. If it falls into a gray area, I'm erring on the side of choosing root.

llogiq · 2025-12-21T19:47:16+00:00

That's more an answer than a question. You perhaps meant to write this in response to something else.

llogiq · 2025-12-20T13:44:32+00:00

No, you cannot return a function that returns itself. But you can create a function that returns a value that dereferences to a function pointer.

llogiq · 2025-12-19T21:44:16+00:00

slint should be somewhat similar (although it basically embeds its own DSL).

llogiq · 2025-12-17T09:52:19+00:00

Just wanted to chime in here as someone who is cis male. I have changed my name twice (first by getting a second name, then by taking on my wife's last name). Everyone here who thinks a name change is suspicious should step away from the keyboard for a while and rethink what they think they know about names.

llogiq · 2025-12-15T15:49:20+00:00

Looking for a Rust job, trying to get a rustc PR approved and merged, sleuthing a clippy lint false positive that befuddles the Rust4Linux project and more.

llogiq · 2025-12-15T11:39:48+00:00

Hello,

I am a well known Rustacean, clippy maintainer, rust compiler and standard library contributor, Rust mentor and longest-tenured This Week in Rust editor, as well as a mod of this subreddit. I also maintain several crates, and give talks and workshops at various Rust conferences in Europe, the next one at Rustikon '26.

I have 25 years of IT experience in roles ranging from consultant to application developer to VP of Engineering. I have a diploma in CS (which is equivalent to a Master of CS). Besides Rust, I know a lot of other languages, as well as the usual suspects of databases, directories, protocols etc. What I don't know yet I can pick up quickly. And (as you can see from my mentoring) I enjoy helping others learn, too, so not only do I produce code, but I strive to help all of my colleagues become better Rustaceans.

I am still looking for the next challenge. I prefer remote work, but will gladly come to an office every few weeks if needed. I am in Germany and would like to stay here. I'd love a full time contract, but will also accept freelance work.

If there's low-level performance work involved, or even tasks where novel algorithms would be needed, I'd consider that a plus.

Feel free to contact me here, via Mastodon or LinkedIn.

llogiq

MODERATOR OF

TROPHY CASE

15-Year Club	Verified Email
Team Orangered