reading 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 :/
@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
musl - Re: [SC22WG14.35974] N3849 - Memory allocation with size feedback v2, request for feedback

@astraleureka i do not buy the gcc hate

@astraleureka

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

@astraleureka holy shit

It doesn't take a rocket surgeon to figure out that an allocator- aware std::vector would be a marriage made in heaven:

@astraleureka this is remarkable

C++'s assumption of non-relocatable values hurts everybody for the benefit of a few questionable designs

@astraleureka using template structs and not concepts in TYOOLinus 2026? you are going to lose subscriber!
@astraleureka OMG they mention their fucking meme memcpy at the bottom