Thread with 1 post
jump to expanded post
"Were multiple return values go's mistake?" asks someone on their blog.
I don't think so. Go's bread and butter are functions and data structures. Chunks of data in memory. And your functions operate on them. You pass in a few, you get a few others back, very, very natural.
It was wrong (it wasn't) so I corrected them (I didn't).
All in all, not a complete waste of time. At least I'll have at least one entry in 2025 in my blog :)