the vessel of morgannareading a thread on the musl mailing list with a patch replacing the iswalpha/iswpunct functions with a compressed LUT, the code is clever, functional *and* better for the common cases, but the submitters replies very strongly smell of chatbot slop :/
d@nny disc@ mc²@astraleureka what is a LUT
@hipsterelectron a lookup table
@astraleureka the facebook guy here saying yeah we decided to do things a nonstandard way https://www.openwall.com/lists/musl/2026/03/24/2 reminds me of zstd who has their own memcpy "WILDCPY" with safe 16 bytes of overwrite and then a week later i find they strictly benchmark in-memory
@astraleureka i do not buy the gcc hate
To see why that's the case, consider a large vector of capacity C.
getting paid the big bucks to consider a large vector of capacity C
@astraleureka i definitely call bullshit on this lowercase k. pretty sure that is doing induction and then changing the counting variable into a rational
@hipsterelectron ohhh this is the {re,m}alloc with feedback thread.. i have been at least partially following this and the amount of bikeshedding glazed my eyes. i do not understand the motivation for fuzzy chance of slightly more space being returned from an allocation request when in the vast majority of cases you're going to need a whole lot more code on the consumer side to handle those cases where you get back more than you requested, isn't that going to eat up the really small number of cycles you could potentially "save" in the rare chance that you do get an expandable slice of memory that isn't already bounded by other allocations
@astraleureka oooh i buy your framing i'll read
@astraleureka yes wtf lmao
@astraleureka i'm a huge believer in scoped allocators as a conceptual measure just bc it's technically more information for the allocator to have a tagged set of users. but i also think i want a slightly more thoughtful and extensible way to handle those guarantees beyond rust's single scope at a time. i have been surprised that non lexical lifetimes were a solution to a problem
@astraleureka everything the fb guy is saying is weird and the intrinsic mention is funny when rust has this guy from google going yeah we do this crazy specific thing in llvm it's in the file that doesn't exist
The C intrinsics work around this by reversing the element ordering in vectors before & after each intrinsic. We need to do the same in stdarch.
@hipsterelectron What the Fuck
@hipsterelectron completely unrelated but oh shit I know Amanieu from way back in the day, he used to be active in the tremulous (q3 full conversion mod) community back in like 2006-2009
@astraleureka he made a rust PR that was unrelated to this in 2023 changing tons of architecture directives across the repo and then went to the ahash repo and said sorry you broke the nightly i didn't release yet with no title or description so i find him curious but i actually have to admit the blue green is a really nice color
@hipsterelectron back in the trem days he authored the most popular qvm (quake VM) patchset for better moderation and game config tools, he was a pretty crucial part of keeping that community alive after the official devs kinda fell off
@astraleureka that sounds kind of unbelievably cool
@hipsterelectron it was a pretty magical time imo, several thousand players all over the world, fully open source game, it's where I cut my teeth on real world C and fleshed out sysadmin skills. my biggest accomplishment during that time was sql integration into the server to manage user tracking and logging. nowhere near what the actual wizards like amanieu or lakitu7 were up to though.
the game is pretty much undead these days, few servers still up but generally 0 players :(
the game is pretty much undead these days, few servers still up but generally 0 players :(
@hipsterelectron I was also a really notorious forum troll in the community too so there's a lot to be embarrassed about, reading my old posts is So Bad