The Rust compiler suffers from a number of crash bugs and nondeterminism, and they won't accept AI diagnoses or fixes, so Rust has become an unreliable partner for software development.

If you're going to do serious development with Rust, I suggest forking the compiler. Upstream your fixes to a fork which takes AI contributions, or fork your own. Or keep all of your improvements private, that works just fine.

Author here: An apology on the graphs, they just count rust files touched in commits, not total commits. So if there were two commits and one touched 3 .rs files and another touched 2, it'd be counted as 5 for the purposes of the graphs. I may fix this later but, yeah.

the author wrote a whole blog post asking how the bun rewrite is going and the answer from the thread is: nobody knows, including the author

This doesn't answer the question posed in the title unfortunately. I am none the wiser about how it's going. The author just speculates that the rewrite isn't actually complete.

Coincidentally - I'm trying to get feedback on my own LLM rewrite project - MAME ROM machine code to Idiomatic JavaScript - the ability for an agent to understand blind code is remarkable.

But sadly HN is hiding my post... :(

https://news.ycombinator.com/item?id=49069383

EDIT: I'd love to hear why I'm downvoted.

[dead]

[dead]

Rust devs are so obsessed with writing things in Rust that Rust was re-written in Rust.