![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/V3gyxs4Ucn.png)
IIRC it’s an APU thing, and last I heard it was just a rumor (could be out of date). Either way, non-LTSC is EOL in a year and a half. If you’re putting in a Zen 5 CPU, the best choice is realistically either Linux or Windows 11 Pro, since Pro can turn off all the bullshit through group policy. My Windows machine I have to have is on 11 Pro and it’s basically Windows 10 with a slightly different taskbar. No Copilot bullshit, no ads, no Bing in Windows Search. If you’re ok your taskbar on the bottom of the screen, IMO it’s the best choice as long as you have to use Windows.
This is a use-after-free, which should be impossible in safe Rust due to the borrow checker. The only way for this to happen would be incorrect unsafe code (still possible, but dramatically reduced code surface to worry about) or a compiler bug. To allocate heap space in safe Rust, you have to use types provided by the language like
Box
,Rc
,Vec
, etc. To free that space (in Rust terminology, dropping it by usingdrop()
or letting it go out of scope) you must be the owner of it and there may be current borrows (i.e. no references may exist). Once the variable isdrop
ed, the variable is dead so accessing it is a compiler error, and the compiler/std handles freeing the memory.There’s some extra semantics to some of that but that’s pretty much it. These kind of memory bugs are basically Rust’s raison d’etre - it’s been carefully designed to make most memory bugs impossible without using
unsafe
. If you’d like more information I’d be happy to provide!