Zig Creator Calls Spade a Spade, Anthropic Blows Smoke

Re:Zig Creator Calls Spade a Spade, Anthropic Blows Smoke by selfmodruntime on Monday July 13, 2026 @10:03AM (#48892878)

This isn't propaganda, the Rust compiler's rules when using the unsafe keyword are difficult to uphold, which is why the community wrote Miri.

[ Parent | on HN ]

Re:Zig Creator Calls Spade a Spade, Anthropic Blows Smoke by Ygg2 on Monday July 13, 2026 @12:02PM (#48894706)

Ok, and how does, in your opinion, compiler rules enforcement work in an unsafe block?

And how does Miri help solve this issue?

[ Parent | on HN ]

Re:Zig Creator Calls Spade a Spade, Anthropic Blows Smoke by selfmodruntime on Monday July 13, 2026 @05:08PM (#48898909)

> Ok, and how does, in your opinion, compiler rules enforcement work in an unsafe block?

By the engineer's wit of course!

> And how does Miri help solve this issue?

By detecting undefined behavior caused by violation these rules

[ Parent | on HN ]

Re:Zig Creator Calls Spade a Spade, Anthropic Blows Smoke by dwattttt on Monday July 13, 2026 @06:02PM (#48899510)

Is there a "Rust compiler's rule" you can point to that's harder than avoiding UB in C or C++ in similar circumstances? They strike me as very similar beasts.

[ Parent | on HN ]

Re:Zig Creator Calls Spade a Spade, Anthropic Blows Smoke by Ygg2 on Monday July 13, 2026 @10:22PM (#48901528)

> By the engineer's wit of course!

Seeing how the Rust compiler isn't an LLM, it can't really work on wit.

From the POV of a programmer, how would you implement an unsafe block? What is disabled vs what's enabled?

> By detecting undefined behavior

Say you are tasked with making Miri; how do you detect violations of these rules?

[ Parent | on HN ]