Our great sponsors
-
tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
rio
pure rust io_uring library, built on libc, thread & async friendly, misuse resistant (by spacejam)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
See: many resolved I-unsound issues in rust stdlib. Some found and addressed by looking at the problematic code snippets.
"damn good reason" is subjective. Is this a damn good reason? Why not just use a Mutex? What about this?. Context matters.
I was going by this issue, which is just a generic highly-upvoted consensus builder against unsafe without any reference to an actual problematic example. The confirmation of unsoundness came after the original post had drawn lots of eyes and people started probing it.
It's like cargo should have a way to mark a dependency as unsafe. That way, you could have a safe mmap crate as an unsafe dependency. Or something like rio which is deliberately unsound (but is fine if you abide by its rules through the entirety of the program)
But then this issue seems to have been closed...