> Also tuples.
A tuple is just a makeshift struct. Think about it this way: by replacing it with a real struct, you're documenting your code.
A tuple is just a makeshift struct. Think about it this way: by replacing it with a real struct, you're documenting your code.
This is what it feels like going from a language with tuples, to one without :)
(I would also say "imagine further that you had to do the same whenever you returned multiple values"--but you don't have to imagine ;)
The only thing missing is giving a tuples a name. But if you do that, you should make a struct, or you will forget which field is which and have bugs.