robotgirlfucking, or as i call it, a cock in the machine
Remote
Mira, Lady of the Kenrei Gate
@specificprotagonist@tech.lgbt
mastodon 4.7.2+glitch.techlgbtvery cuddleable and biteable
not very safe for work
geeignet, den öffentlichen Frieden zu stören
"simultaneously intelligent and very dumb"
– @valuepackcatgirlad@fed.amazonawaws.com apparently
╱|、
(˚ˎ 。7
|、˜〵
じしˍ,)ノ
93 Followers
106 Following
33 Posts
Joined June 26, 2023
pronouns:
she/they/it
geospatial:
saxony
lang:
eng | de | tok (lili)
error[E0275]:
overflow evaluating the requirement `&_: IntoIterator`
flirting:
sure :3
Kagi likes making it very clear it's a search engine, not a find engine
Having the train for just yourself and your girlfriend is quite nice.
it seems like my train chair considers it its paramount duty to electrically shock me
pff, i can take a tree in a fight. they're all bark and no bite
preboob execution environment, aka childhood home
Replying to
have some more :3
made a hashmap that only allows inserting & looking up entries, not removing or mutating them
but in return lookups can be concurrent with writes yet stay fast no matter how many threads you use :3
i love wiktionary
oh: door dash for boobs
Choo choo!
gotta finally try out uiua
oooh, the European Tramdriver Championship is in 2 weeks? :blobcateyes:
öffentlicher Personengeschlechtsverkehr
i love clicking on old links to docs on Microsoft Developer Network and getting redirected to the front page instead, very helpful
Self-OH: "That's the amazing power of boobs!"
how is github finding new and exciting ways to fuck up
I see some discussion about Fil-C online, but what kinda gets lost among the performance/memory overhead, limited platform support, and runtime-vs-compiletime detection is that its only memory-safe for a very weak form of memory. That is, as far as I can tell it
- detects (most) out of bounds accesses that aren't legal in C (invisicaps)
- makes use-after-frees that aren't legal in C behave as if the memory hasn't been freed yet (garbage collection)
- zero-initialize allocations & define some normally UB operations, e.g. legalizing out-of-bounds pointer arithmetic
For one, this means it doesn't fully deal with unsynchronized accesses or reads from the wrong union field, even when they are illegal in C and would usually be considered memory safety violations.
But the other thing is that C is not designed for memory safety, and so it allows lots of accesses because it doesn't give you the tools to declare what is valid or not.
1/2
neat, nixos-rebuild has a --sudo flag which makes it only escalate privileges once they're needed, so you kick of the rebuild and then it sits silently in the background waiting on a password prompt while you're not thinking about it :p
transfem mathematician planning her bottom surgery be like
Replying to
@konstruct@woof.tech @Natasha_Jay@tech.lgbt Thanks. That explains why the prose was so awful.
Replying to
@flora Same :3
(and have it set as the default branch name)
Replying to
@ueckueck@dresden.network Eine extrem schmerzhafte, teils tötliche Waffe zur Deeskalation zu nutzen beweist beeindruckende Kreativität.
Replying to
Replying to
@Mico_PsyOp_Catgirl@fedi.ars-cotidiana.eu the way into a beepers heart is their /etc/sudoers
Replying to
@AllieKoba@girlcock.club Pretty!
Replying to
@mei That's a great article. And terrifying indeed. Hats off to their team for debugging this.
Now I'm thinking back to a locking primitive I implemented that uses a similar linked list of (per thread, per cpu) structures. And that despite being a far, far simpler situation (entirely userspace), I still have a deadlock somewhere :p
totally doesn't make me wanna learn enough to be able to write a machine-checkable proof of it being deadlock-free
Replying to
@vgarzareyna@mstdn.mx @cliffle@hachyderm.io @Mara@hachyderm.io I believe that they decided that the Safe C++ project required too many changes not just in C++ the language but also in replacing unsafe interfaces, and that they will just use a silver bullet instead.
Replying to
@julia infosec advice: permanently encrypt your paper records by burning them
Replying to
@terts@mastodon.online @jana@fedi.xirion.net the type inference here is what I would have expected, but huh didn't know that the right-hand side pf @ patterns could introduce identifiers too, that's funny :3