News for hackers. Stuff that matters.

A comment on How Our Rust-to-Zig Rewrite Is Going. Parent comment

Re:How Our Rust-to-Zig Rewrite Is Going by maybebug on Thursday July 16, 2026 @08:42PM (#48942119)
Memory safe languages, where usage of Miri and Valgrind (tools to for instance debug memory unsafety) are common and integrated into CI for some of the projects in the language. Even some Rust guides encourages running Miri in CI https://microsoft.github.io/RustTraining/engineering-book/ch... . Searching on GitHub yields a lot of projects that run Miri in CI. And there have been a lot of CVEs for Rust projects caused by memory unsafety.

Interesting perspective that you have.

[ Parent | on HN ]
Re:How Our Rust-to-Zig Rewrite Is Going by pjmlp on Friday July 17, 2026 @01:46AM (#48943721)
People still die while wearing helmets and seatbelts.

Yes, those unsafe blocks should be cross checked, but lets not pretend it is the same as writing C or C++ where each line of code is a possible CVE.

[ Parent | on HN ]
[dead]
Re:How Our Rust-to-Zig Rewrite Is Going by pjmlp on Friday July 17, 2026 @05:51AM (#48945310)
Not at all, my buddy, my original point stands.

Do you think personal attacks affect me? Grow up, I have cut my scars in the bloody discussions from BBS and Usenet days, not the woke friendly discussions of modern Internet.

[ Parent | on HN ]