Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bun's unreleased Rust port has 13,365 unsafe blocks

bun.com

Post reply on HN
Print view View original

41–50 of 57 posts

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#41

Post by vrmiguel »

charcircuit wrote: post #24
mariopt wrote: post #7

The current level of insanity with AI is off the charts. Porting to a safe language without the safety features.

C2Rust, the most popular transpiler from C to Rust will leave a bunch of un safe blocks. After the initial port it is expected for the authors to go in and work to remove them.

But if that's the goal then I _think_ the "port" is perfectly achievable without LLMs. Zig transpiles to C, then C2Rust would do the rest

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#43

Post by charcircuit »

vrmiguel wrote: post #41
charcircuit wrote: post #24

Earlier quoted context omitted.

C2Rust, the most popular transpiler from C to Rust will leave a bunch of un safe blocks. After the initial port it is expected for the authors to go in and work to remove them.

But if that's the goal then I _think_ the "port" is perfectly achievable without LLMs. Zig transpiles to C, then C2Rust would do the rest

There's more than one way to crack an egg.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#44

Post by xigoi »

dgellow wrote: post #26
izietto wrote: post #23

Guys, does anyone know why the decision to port Bun from Zig to Rust? Is it to move to a less niche language?

The bun team communicated about it, it’s to reduce the number of memory issues they have to deal with IIRC

I wonder if the actual reason is that Zig declined their slop PR.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#47

Post by ryanshrott »

13k unsafe blocks is a reminder that unsafe on its own isn’t the problem, it’s whether that unsafe boundary is small and audited. The number that matters more is how much of the codebase depends on unchecked invariants. If the answer is most of it, the port is moving too fast.

Re: Bun's unreleased Rust port has 13,365 unsafe blocks

#49

Post by PufPufPuf »

000ooo000 wrote: post #46
PufPufPuf wrote: post #45

If you want to dig into Bun's port to Rust, I suggest waiting until they actually release something instead of generating LLM slop charts about unfinished source code.

This is posted by Bun on bun.com

Oh, I didn't notice the URL, the page didn't seem at all official. In that case it's weird that they present this clearly LLM-generated "report".
Post reply on HN