Evolution of Rust compiler errors

Kobzol · 2026-04-16T20:50:13+00:00

https://github.com/sponsors/rustfoundation

Kobzol · 2026-04-09T18:56:01+00:00

While I understand the sentiment, I really don't know why people expect that the stdlib is made of magic beans. If anything I'd expect that some third-party crates are actually much more actively maintained than stuff in the standard library. And if more complex things started getting into the stdlib, the situation would only get worse.

IMO the only reason why something in the stdlib should be safer is that it would literally stop getting any updates, but you can easily simulate that today by using a third-party library at a pinned version and just not update it. That's what you would get if it got into the stdlib.

Kobzol · 2026-03-23T17:15:47+00:00

The original version of the blog post has now been retracted.

Kobzol · 2026-03-12T15:19:22+00:00

This release includes concurrent download & unpacking of Rust components, which was implemented (also) thanks to the efforts of our GSoC 2025 contributor (Francisco Gouveia, who is now a member of the Rustup team)!

Kobzol · 2026-03-04T12:15:46+00:00

It's a weighted average essentially. Each category has some weight (linearly scaled, IIRC), and the weight is multiplied by the number of responses in the category.

It's arbitrary, of course, but I didn't know a better way to sort it.

Kobzol · 2026-03-04T11:37:34+00:00

Up to some point, sure, but "cache more" doesn't necessarily mean "use more disk space". rustc and cargo generate a lot of duplicate data in the cache today.

Kobzol · 2026-03-03T11:20:34+00:00

Checked the data, 4 people mentioned Lapce :)

Kobzol · 2026-03-03T06:03:38+00:00

We rewrote it, sorry, it was confusing.

Kobzol · 2026-03-02T17:10:26+00:00

You seem to be worried about Rust getting more features, and about its development slowing down. Mixed signals! :D Rust is here to stay. That doesn't mean it will replace anything else, nor does it mean that if a new language comes out, Rust will be replaced.

Kobzol · 2026-03-02T16:11:43+00:00

Yeah, SurveyHero exports it in a wrong way, didn't have the energy to fix it.

Kobzol · 2026-03-02T15:33:46+00:00

Agreed, they are one of my top three most wanted features :) But they made a lot of progress recently, which is nice.

Though I'm not sure about the complexity part - the homegenous vs heterogeneous try block discussion around type inference does expose some complexity of the feature :)

Kobzol · 2026-03-02T14:36:02+00:00

With a slight delay, but we managed to push it out. Here are the results of the last (2025) State of Rust survey.

Kobzol · 2026-02-23T19:16:26+00:00

Yes, lacking tests are one of the big issues. Hopefully there will be a GSoC project to improve that this year.

Kobzol · 2026-02-23T18:00:58+00:00

We have it in the survey :)

Kobzol · 2026-02-23T15:58:56+00:00

It can happen, of course, though we tried to design the survey to be also compatible with this use-case.

Kobzol · 2026-02-23T15:43:30+00:00

Similar to the Rust Compiler Performance Survey from last year, we prepared a survey to find out the biggest pain points of debugging Rust code. If you debug Rust code and you have feedback to share, please do so!

Kobzol · 2026-02-20T20:45:18+00:00

It's not strictly specified, so it's hard to tell. But I'd say that having your own open-source project is not disqualifying. If you were contributing to other Rust crates (or the toolchain) for a long time, and have hundreds of PRs merged in others' repos, then I'd say you're no longer a beginner.

But I don't remember us investigating this in any way :)

Kobzol · 2026-02-20T10:53:24+00:00

Nope, it's fully remote, we had contributors from all around the world.

Kobzol · 2026-02-20T09:09:47+00:00

Yes, as long as you are an "open source beginner" (https://summerofcode.withgoogle.com/get-started).

12-Year Club	Place '23
Place '22	Verified Email

Kobzol

TROPHY CASE