News for hackers. Stuff that matters.
Re:Three Minor Features in Go 1.18 by awinter-py on Wednesday December 22, 2021 @07:04PM (#29657091)
agree -- ultra useful alternative to splitting

would be neat to imagine a language where this was an optimizer feature rather than a decision the programmer made. many functions that return an array are ultimately using just one, or a few elements of it. the compiler can make a lot of decisions in the caller about how to reduce allocation or short-circuit array processing.

I think, but am not sure, this is what the experimental parsing language 'wuffs' is about https://github.com/google/wuffs -- the language itself is aware of array lengths as a first-class citizen and can make decisions accordingly

Re:Three Minor Features in Go 1.18 by tialaramex on Thursday December 23, 2021 @12:03PM (#29663758)
WUFFS is, as it's name suggests, primarily about safety, but it gets performance advantages that fall out of safety (e.g it needs no runtime bounds or overflow/underflow checks because it proved these things can't happen at compile time)
Re:Three Minor Features in Go 1.18 by layer8 on Wednesday December 22, 2021 @08:34PM (#29657700)
The optimization could be done by lazy evaluation, like a generator.