Since the x/exp/maps era, I have used maps.Keys and maps.Values extensively. They are very useful and avoid users from doing loop iterations.
I remember that they were added to the standard library, but I used maps.Keys in the latest go version and was surprised that it could not compile. By looking at the source code, I found that their behavior seemed to have changed for iter? Related discussions: https://github.com/golang/go/issues/57436 https://github.com/golang/go/issues/61538 Maybe I have limited information and less knowledge than the members of the go team, but if it is to support the functions of the iter package, why not add two new function names, such as maps.KeysIter and maps.ValuesIter, instead of changing the behavior of the previous method? In addition, how do you deal with the scenarios previously handled by maps.Keys? Do you do it manually with for ..range..append, or use golang.org/x/exp/maps? Is it necessary to propose a proposal to add these two methods back to the standard library, but with different names? -- 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/4f95be15-1a7d-4cb8-a19d-eb33a1736d68n%40googlegroups.com.
