Re:Rust Performance Pitfalls
by steveklabnik on Thursday June 08, 2017 @12:51PM
(#14515398)
The nature of undefined behavior is in fact super vague; it's not actually possible to say what will happen.
[ Parent
| on HN ]
While technically true, a specific example helps the reader conceptualize what level of danger that means, when they don't already have a concrete understanding like you do. Recall that the breadth of experience for rust's userbase is much larger than e.g. C.
Re:Rust Performance Pitfalls
by steveklabnik on Thursday June 08, 2017 @02:24PM
(#14516027)
Oh yeah, I mean, I'm not saying I disagree with adding detail, I can just see the impulse to not, since anything you say may or may not be true.
me talking about rust's userbase
steveklabnik's profile: "Rust core team"
I'm guessing you know that a lot better than I do lol.
Re:Rust Performance Pitfalls
by steveklabnik on Thursday June 08, 2017 @02:54PM
(#14516250)
It's all good! You're absolutely right, and it's easy to forget when you're inside a bubble.
Re:Rust Performance Pitfalls
by TickleSteve on Thursday June 08, 2017 @03:48PM
(#14516676)
> breadth of experience for rust's userbase is much larger than e.g. C
Really? I think you mean the opposite here.
Re:Rust Performance Pitfalls
by steveklabnik on Thursday June 08, 2017 @03:54PM
(#14516725)
I read this as saying "not depth", that is, C programmers will have a deep understanding here, but since Rust is drawing in a lot of new blood, they on average will not.
Just say the worst thing that can happen, out of bounds access probably qualifies. :-)