The probability that someone would ship something so bogus is so tiny compared to how often string.h is misused as to not be comparable.
-
-
-
It’s like saying unsafe lets you violate memory safety in Rust. Sure it does. But memory safety problems happen WAY LESS in Rust than in C.
- 2 more replies
New conversation -
-
-
It’s in secstr on crates.io. https://github.com/myfreeweb/secstr/blob/master/src/lib.rs#L72 …
-
Dependencies are easier in Rust than in C due to better integration with Cargo. People reinvent the wheel less in Rust than in C.
- 13 more replies
New conversation -
-
-
Not the fault of the language.
-
string.h APIs are terrible. That is a fault of C.
- 3 more replies
New conversation -
-
-
You don’t vendor crates.io packages. Also, Go’s standard library is too big for Rust. But yes, I agree, let’s get it into the Rust nursery.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I feel folks aren’t calculating probability of misuse. A footgun named “string compare” in libc vs. a function you’d have to write yourself.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Timing attacks are way less severe than this.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think that’s wrong (if that were true, you couldn’t write anything in e.g. Python), but this has gotten too off-topic for Twitter.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.