this post was submitted on 30 Dec 2024
5 points (56.4% liked)

Rust

6216 readers
4 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
5
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/rust
 

There are endless debates online about Rust vs. Zig, this post explores a side of the argument I don't think is mentioned enough.

Intro / TLDR

I was intrigued to learn that the Roc language rewrote their standard library from Rust to Zig. What made Zig the better option?

They wrote that they were using a lot of unsafe Rust and it was getting in their way. They also mentioned that Zig had “more tools for working in a memory-unsafe environment, such as reporting memory leaks in tests”, making the overall process much better.

So is Zig a better alternative to writing unsafe Rust?

I wanted to test this myself and see how hard unsafe Rust would be by building a project that required a substantial amount of unsafe code.

Then I would re-write the project in Zig to see if would be easier/better.

After I finished both versions, I found that the Zig implementation was safer, faster, and easier to write. I’ll share a bit about building both and what I learned.

you are viewing a single comment's thread
view the rest of the comments
[–] sudo 4 points 2 weeks ago

The article title is poorly written but the conclusion is pretty sound: If you're planning on writing unsafe code, use a language meant for unsafe code. Zig is meant for unsafe code, Rust isn't.