labeling sexual content is part of consent culture.

the way that you square the two principles "we should be able to share our bodies fearlessly and shamelessly" and "we should be able to control our own engagement with sexual interactions" is labels.

so why are we always complaining about labels?

as is, even requiring borrows be 'static can't save you, it's so rough

we need 'cursed

lifetime's haunted

oh nice I didn't know about this one!

in my ideal, you should be able to have like, a Cursed Lifetime, that makes it so stuff can't go into allocated storage or be forgotten. bc lifetimes guarding a DMA doing shit at the silicon level are like the nuclear waste of lifetimes. they need special care.

they could at least guarantee destructors in heapless environments 😭 you *can* make a strong guarantee if you don't allocate, but because it's impossible in alloc environments, now us innocent heapless devs have to deal with mem::forget being marked safe. [shakes fist at devs using the Big Computer]

DMA allows you to do operations like "copy stuff from [0x20, 0x30) to [0x80, 0xFF) and loop to the start of the source buffer each time you hit the end" with equal or less overhead as memcpy code. in another world, we could have given memcpy enough argument degrees of freedom to represent this.

there's a stale issue on a repo i frequent where someone says "your DMA interface is safe over dropping but not forgetting" and the response is "huh, guess it is. wonder if that's possible to fix."

[zero activity on the issue ever again]

just dont forget or construct situations that forget. ez

...DMA is kinda a glass houses thing though because the whole "mem::forget is safe" thing means it's pretty much impossible to write a safe DMA API in rust, the language isn't prepared to cope with "a piece of hardware can keep executing instructions even if everything referring to it is forgotten"

also it's famously a pain in the ass to verify that the regions you're passing to memcpy are the same length.

and assuming they're the same length restricts the memcpy interface such that it can't represent certain copies that are just as cheap on certain architectures (e.g. looped range via DMA)

we must cultivate the skill of saying "getta load of this bullshit" when the bullshit happens instead of wondering aloud if This Is The Big One

[remaining audio unintelligible over the sound of malloc grinding and sputtering as it hits the corrupted inline metadata]

C enjoyer: "passing fat pointers for slices pales in comparison to my solution utilizing the raw efficiency of C: i pass a thin pointer to an array... and a size_t for how long it is. this is not a fat pointer because i wrote it manually in two arguments so it Feels Efficient."

i know that rust having arrays not generic over their size was a headache for trait implementation, but the period of time before const generics fixed that were honestly probably good for forcing all the grumpy C converts to learn to use a slice correctly instead of jamming generic arrays everywhere

you are infinitely more useful to our collective survival on the outside, working towards the day we're all free.

...but if you're not up for that amount of work, at least don't make it harder by throwing yourself on the pile.

what if instead of 1000 white collar workers commuting daily to the city from their "farms" (big house in the middle of land they lease to an actual farming business) we had 10 farm operators/laborers commuting daily from the city?

sorry this isn't possible because farmer on bus too woke

this is from a *winnie the pooh* film (1997)

every idiot who actually says with their full chest "my alternative to prison is mob violence" makes me just as angry as the people who cheer for the prison torture. both of these options are sociopathy.

oh, and someone found concrete evidence for the (already fairly obvious) vibe that they're one or more right wingers having a laugh!

bsky.app/profile/kuro...