>>106533046
Your data does not match what lib.rs reports.
What happens if you include tokio, and the 15 most popular crates, and the 15 most starred Github projects?
And when you write
>unsafes
does that refer to occurrences of the unsafe keyword or the number of lines contained in each unsafe block? Some unsafe blocks can be ridiculously long.
https://github.com/rust-lang/rust/tree/master/library/core/src/slice/sort
4chan Search
2 results for "9dfde8030c0f154e1571cc7ef5b5b94d"
Why does efficient implementation of common algorithms in Rust require unsafe all over the place?
Just look at this shit:
https://github.com/rust-lang/rust/tree/master/library/core/src/slice/sort
There is unsafe all over the place in the source code in these folders, including giant blocks of unsafe as part of implementing algorithms.
Why does Rust force developers to learn the intricacies of unsafe and bear the maintenance burden of unsafe when they want to implement common algorithms like sorting algorithms efficiently?
The Rust standard library has had at least several occurrences of undefined behavior and memory unsafety, so don't tell me that unsafe is fine. https://materialize.com/blog/rust-concurrency-bug-unbounded-channels/
https://github.com/rust-lang/rust/tree/master/library/core/src/slice/sort
There is unsafe all over the place in the source code in these folders, including giant blocks of unsafe as part of implementing algorithms.
Why does Rust force developers to learn the intricacies of unsafe and bear the maintenance burden of unsafe when they want to implement common algorithms like sorting algorithms efficiently?
The Rust standard library has had at least several occurrences of undefined behavior and memory unsafety, so don't tell me that unsafe is fine. https://materialize.com/blog/rust-concurrency-bug-unbounded-channels/