> Please note that "maps.Collect" is slow. https://github.com/golang/go/issues/68261
Please note that I did address that in my message. CollectN matters most for non-trivial iterators, e.g. where you first transform an iterator using `xiter.Map` or the like. Something like slices.Collect(maps.Keys(m)) - which this discussion is about - can be relatively easily optimized by the compiler, if we want. > This is typical micro benchmark. There are too such "allocating and then throwing away small slices" cases in Go programming. The iterator cases are just a tiny portion of them. I was talking about end-to-end execution time of the program. In a CPU-bound program, it is not uncommon for allocations in the inner loop to have significant effects. -- 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/CAEkBMfEhrAheD2MkWrg2UKEWn38wqTZ994GrbJW6EZJVq-byxg%40mail.gmail.com.
