Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by swiftcoder on Friday May 15, 2026 @02:54PM
(#48152400)
Yeah, exactly. The typical approach is to do a mechanical translation such as with rust2c, that is full of unsafe, and then gradually refactor safety in.
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by Dylan16807 on Friday May 15, 2026 @03:00PM
(#48152477)
But nobody makes announcements and blog posts about running that.
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by pgporada on Friday May 15, 2026 @03:20PM
(#48152694)
There's several blog posts here. https://www.memorysafety.org/initiative/av1/
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by Dylan16807 on Friday May 15, 2026 @03:26PM
(#48152762)
And the first post is about the team working on the project, with about two and a half sentences on c2rust, and making it very clear they just started.
The newer posts go into detail about the rearchitecting that follows.
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by Ar-Curunir on Friday May 15, 2026 @03:16PM
(#48152654)
And indeed, the bun team has not done that
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by Dylan16807 on Friday May 15, 2026 @04:15PM
(#48153274)
Did they not make the announcement? And they definitely promised a blog post even if it's not out yet.
Re:Bun Rust rewrite: "codebase fails basic miri checks, allo...
by Ar-Curunir on Friday May 15, 2026 @05:12PM
(#48153924)
Not on their blog, website, or twitter, so no?
They did cite Rust's safety as a motivating factor for the port. That doesn't imply trying to achieve that simultaneously with the language change — which is good, because that would be insane. (Or, if you prefer, even more insane.)
You cannot faithfully port a codebase to a new language while also radically re-architecting it. You have to choose.
They want the safety benefits of Rust going forward; i.e., after it's finished, when they then write new code in Rust.