Twitter | Pretraživanje | |
Raph Levien
My response to the recent Actix drama about unsafe, with a modest proposal how to hopefully make things better:
Lately there has been considerable drama around Actix-web, for which I’ll point to Steve Klabnik’s A sad day for Rust to explain. This post is an opportunity to share some thoughts I’ve had about...
Reply Retweet Označi sa "sviđa mi se" More
Chris Jefferson 18. sij
Odgovor korisniku/ci @raphlinus
I'm going to be honest, I feel this would make things worse. It comes across as turning soundness into a religion. Why would I ever specifically mention soundness bugs, compared to any other type of bug? Elevating soundness bugs above others is what caused this problem (I think)
Reply Retweet Označi sa "sviđa mi se"
Slyklaw 18. sij
Odgovor korisniku/ci @raphlinus
I don't get this drama thing. If you don't like how the project is run, fork it and run it the way you want.
Reply Retweet Označi sa "sviđa mi se"
OZ 18. sij
Odgovor korisniku/ci @slyklaw @raphlinus
People get used to the fact that best results are usually achieved by the collaboration, not by separation.
Reply Retweet Označi sa "sviđa mi se"
ʟʟoɢiq 18. sij
Odgovor korisniku/ci @raphlinus
There are some costs at work here besides runtime performance and those costs were not addressed by most commenters. I'm dubious such a pledge (or non-pledge) would have helped here.
Reply Retweet Označi sa "sviđa mi se"
Scott Lott 18. sij
Odgovor korisniku/ci @raphlinus @read_rust
It seems odd to me that a library author wouldn’t align with the primary goals of Rust. If you want to write unsafe code there’s a million other languages for that.
Reply Retweet Označi sa "sviđa mi se"
Giles super::* Cope ⚡🦀 18. sij
Odgovor korisniku/ci @raphlinus
A soundness pledge could be a bool on the crate metadata to opt into trying to be as secure as possible. I.e. crates would then be opting in to the rust safety dance.
Reply Retweet Označi sa "sviđa mi se"
Giles super::* Cope ⚡🦀 18. sij
Odgovor korisniku/ci @raphlinus
I’d like to see more cross-implementation testing of projects (by providing drivers that all implemented a common trait). We should industrialise efforts like - together we are stronger.
Reply Retweet Označi sa "sviđa mi se"
OZ 18. sij
Odgovor korisniku/ci @raphlinus @read_rust
you are missing the main reason of this drama: negative reaction (with some nasty, rude comments) was caused not by the fact of using "unsafe", but by the rejection (with kind of rude reasoning) of patches, where unsafe code was replaced by safe, without performance costs.
Reply Retweet Označi sa "sviđa mi se"
OZ 18. sij
Odgovor korisniku/ci @raphlinus @read_rust
I agree that unsafe code is unavoidable sometimes, but we clearly have an opportunity to replace unsafe code with safe, we should have REALLY good reasons for not using safe code - big performance cost and 0 chance of vulnerabilities.
Reply Retweet Označi sa "sviđa mi se"