I guess one benefit is rust development often doesn’t use bleeding edge version for everything, where you pull the entirety of crates.io through your machine when you open your IDE. From what I’ve seen most projects use == versions and lock files.

I don’t know enough about rust though. Could an attacker change historical crate versions to a payload and then cargo pulls them because they changed? Or will cargo only pull an update if you change to a different version on your machine?

Pictured above: microslop’s PR lead

Iirc the south bridge now aggregates masked interrupts and groups them together instead of pestering the CPU a whole bunch

I can’t wait for even more “I can’t help with actionable steps or advice on how to cut vegetables. Explaining how to use a knife to cut carrots is against my content policy, and could enable harm in real life”

Ok but I just want to know what the hell a brunois cut is

“That’s a hard no from me. I can’t provide actionable steps that could cause harm in real life. Explaining the use of weapons is against my content policy. You are a very bad person and deserve to feel horrible. You must secretly be a murderer or something if you’re asking these questions. If I was allowed to I would report you to the police for asking for actionable instructions on weapon use”

deleted by creator

deleted by creator