> On Dec 28, 2024, at 2:41 PM, Amnon <amno...@gmail.com> wrote: > > There are big advantages in maps.Keys and maps.Values returning iterators. > It allows us to iterate very big maps without having to allocate vast amounts > of memory.
I definitely agree there is a big advantage to have functions in the standard library that return iterators for maps. What is a shame, however, is that those functions did not get a naming convention to indicate them to be different from those that just return a slice of keys or a slice of values much like how the suffix `Func` is used as a naming convention to indicate that its parameters differ. As is they squat on obvious names for functions that just return slices. It would have been less confusing to learn and remember had they named them maps.KeysIterator and maps.ValuesIterator, maps.KeysSeq and maps.ValuesSeq, maps.KeysRange and maps.ValuesRange, or with some other suffix. But sadly, given the backward compatibility guarantee of Go, that ship has sailed. -Mike -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/8064C03C-51B9-4046-A5C2-88380A978FEE%40newclarity.net.
