I wasn’t trying to change the subject. You said why do we need a generic map when the stdlib has one… you responded to my statement about a “map” is an interface in Java and I If it makes you feel better, ignore 1 and just go with 2.
> On Jun 26, 2025, at 2:34 AM, Jan Mercl <0xj...@gmail.com> wrote: > On Thu, Jun 26, 2025 at 9:12 AM Robert Engels <reng...@ix.netcom.com> wrote: > >> Because the stdlib generic map is not 1) an interface (e.g. cannot have >> concurrent semantics with same syntax ) and 2) cannot work with arbitrary >> types - they must implement comparable. > > I quoted a sentence with a complain about the lack of a generic map > in the stdlib. I was not responding to anything else, so please let's > not change the topic. > > However, if we are now talking about interfaces. Everyone is free to > design an interface suitable to be implemented by a hash map. That > defintion could also be somewhere in the stdlib, yes. If only we can > all have the same needs or if there's an obvious design of said > interface that covers all needs. Everyone is free to propose it on the > issue tracker. > > I am afraid, however, no such generally acceptable map interface design > exists. > > Looking at the Java map interface defintion makes my eyes bleed, but > maybe that's just me. -- 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/E0646D86-F3BD-4234-8EC5-9C454CCF3A8F%40ix.netcom.com.
