|
|
Log in / Subscribe / Register

Rust "unsafe" is not code the compiler doesn't understand

Rust "unsafe" is not code the compiler doesn't understand

Posted Dec 14, 2025 13:24 UTC (Sun) by mb (subscriber, #50428)
In reply to: Rust "unsafe" is not code the compiler doesn't understand by alx.manpages
Parent article: Rust in Android: move fast and fix things (Google Security Blog)

>standard C is a terrible dialect of C [...]
>Please don't judge C by one of its worst dialects. Those judgements feel disconnected from reality

Judging C by its ISO standard is disconnected from reality?
Really?

Can I tell the trolls that they are disconnected from reality when they demand a Rust standard next time?


to post comments

Rust "unsafe" is not code the compiler doesn't understand

Posted Dec 14, 2025 14:04 UTC (Sun) by alx.manpages (subscriber, #145117) [Link] (1 responses)

> Judging C by its ISO standard is disconnected from reality?
> Really?

Yes. Just like make(1) is a great language (especially, GNU make(1)), and POSIX --and ISO standard-- make(1) is unusable (actually, POSIX.1-2024 seems to have improved make(1) significantly, and some people claim it is now in a usable state; I haven't checked myself, so I can't comment).

As someone said, the standard is toilet paper. Except when it's useful, of course.

> Can I tell the trolls that they are disconnected from reality when they demand a Rust standard next time?

I don't care. I'll only say that I have never demanded a Rust standard.

Rust "unsafe" is not code the compiler doesn't understand

Posted Dec 14, 2025 14:05 UTC (Sun) by alx.manpages (subscriber, #145117) [Link]

> and POSIX --and ISO standard-- make(1)

I meant to write '--an ISO standard--'.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds