Live data from Hacker News

Conc: Better Structured Concurrency for Go

161–162 of 162 posts

Re: Conc: Better Structured Concurrency for Go

#161

Post by mappu » Mon, Jan 23, 2023, 6:11 AM UTC

erik_seaberg wrote: post #91

ikiris wrote: post #72

Earlier quoted context omitted.

don't do that? this kind of thing is why deepcompare exists to begin with

I can nag everyone to use reflect.DeepEqual and live with some false negatives, but maps always use k1 == k2.

This is days later, sorry, but - you can't use an interface as a map key, so this shouldn't apply, right?

Re: Conc: Better Structured Concurrency for Go

#162

Post by erik_seaberg » Fri, Jan 27, 2023, 4:02 AM UTC

mappu wrote: post #161

erik_seaberg wrote: post #91

Earlier quoted context omitted.

I can nag everyone to use reflect.DeepEqual and live with some false negatives, but maps always use k1 == k2.

This is days later, sorry, but - you can't use an interface as a map key, so this shouldn't apply, right?

https://go.dev/ref/spec#Map_types says that is allowed.

> If the key type is an interface type, these comparison operators must be defined for the dynamic key values; failure will cause a run-time panic.

Post reply on HN