this post was submitted on 28 Apr 2026
9 points (80.0% liked)

Rust

7969 readers
35 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
torcherist@programming.dev
9
"AI" audit of rust stdlib (github.com)
submitted 3 days ago* (last edited 3 days ago) by ISO@lemmy.zip to c/rust@programming.dev
8 comments fedilink hide all child comments
 

I checked some of the issues out, and this looks legit. Although a good chuck relates to obscure platform abstractions.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Quantenteilchen@discuss.tchncs.de 6 points 3 days ago* (last edited 3 days ago) (1 children)

I am not an expert but I think the actual problem is in the slice::iter first getting an immutable reference to the underlying data with self.0.next() before mapping it into a UserRef<T> which is instant UB because a &T guarantees exclusivity while UserRef<T> explicitly states in its contract that it does not guarantee anything like that, even if mutably borrowed.

So in essence the problem, as I understood it, is in the step from slice -> reference to value -> User ref of value with the italic part being illegal.

[โ€“] INeedMana@piefed.zip 1 points 3 days ago

I think you put it more understandable