Re:What Makes Code Hard to Read: Visual Patterns of Complexi...
by stouset on Thursday March 13, 2025 @11:34AM
(#43354373)
I was talking more in the general case.
Yes, you can always just write more and more and more code to fix these things. Or you could just… not write more code and still get optimal performance.
Re:What Makes Code Hard to Read: Visual Patterns of Complexi...
by porridgeraisin on Thursday March 13, 2025 @01:43PM
(#43355618)
> just... Not write more code
But the abstractions don't really adapt themselves to be performant in each usecase the way you imagine. I gave an example of c# distinct() above. Sure, they can. But do they? No. They only save anything at all for trivial usecases, where the imperative code is also obvious to parse.
If overallocating is indeed OK for your usecase, then you can do so yourself