Re: [go-nuts] Is it necessary to change the behavior of maps.Keys and maps.Values?

2024-12-29 Thread Mike Schinkel
> On Dec 29, 2024, at 5:11 PM, Axel Wagner > wrote: > > Why don't I use the sequence versions more frequently? Because I try not to > create huge in-memory maps and instead prefer to move logic that manipulates > large amounts of data into a proper database. > > Iterators are more efficient

Re: [go-nuts] Is it necessary to change the behavior of maps.Keys and maps.Values?

2024-12-29 Thread 'Axel Wagner' via golang-nuts
> > Why don't I use the sequence versions more frequently? Because I try not > to create huge in-memory maps and instead prefer to move logic that > manipulates large amounts of data into a proper database. Iterators are more efficient for small maps as well. Allocating and then throwing away sma

Re: [go-nuts] Is it necessary to change the behavior of maps.Keys and maps.Values?

2024-12-29 Thread Mike Schinkel
> On Dec 29, 2024, at 1:38 AM, Amnon wrote: > > A nice thing about Go is that it is easy on the eye. Names are short, and > easy to read. When you look at Go code, you are not faced with a wall of > black text. The signal to noise ratio is high. Variable and function names > general convey wha

Re: [go-nuts] Is it necessary to change the behavior of maps.Keys and maps.Values?

2024-12-29 Thread Mike Schinkel
> On Dec 29, 2024, at 1:28 AM, Axel Wagner > wrote: > > At the end of the day, it's purely a question of what you think would be more > frequently used. That should get the better name. `Values` (as is) composes > naturally with `slices.Collect` and so you get both in one function and it > s