So you can't get a Rust program to segfault without trying really hard. I haven't observed a single segfault in the normal Rust code I wrote in the past 8 years.

[–] apt_install_coffee@lemmy.ml 6 points 8 months ago (1 children)

The code used in cve-rs is not that complicated, and it's not out of the realm of possibility that somebody would use lifetimes like this if they had just enough knowledge to be dangerous.

I'm as much a rust evangelist as the next guy, but part of having excellent guard rails is loudly pointing out subtle breakages that can cause hard to diagnose issues.

[–] technom@programming.dev -1 points 8 months ago (1 children)

If that's so trivial to trigger, people would be doing so everywhere. Have you seen it in the wild or heard of anyone doing so?

[–] apt_install_coffee@lemmy.ml 0 points 8 months ago (1 children)

If someone did, why would I hear of it?

[–] technom@programming.dev 0 points 8 months ago (2 children)

So you're just spouting some cooked up theory. Not a practical scenario.

[–] apt_install_coffee@lemmy.ml 0 points 8 months ago* (last edited 8 months ago)

No, I'm saying that when people run into strange bugs, sometimes they put together an issue (like the person behind cve-rs), and sometimes they quietly work around it because they're busy.

Seeing as I don't often trawl through issues on the language git, neither really involve notifying me specifically.

My lack of an anecdote does not equate to anecdotal evidence of no issue, just that I haven't met every rust developer.