You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
navytux
changed the title
runtime: Invalid "concurrent map writes" after recovered runtime-panic on previous map assign with non-comparable type
runtime: Invalid "concurrent map writes" after recovered runtime-panic on previous map assign with non-comparable key
Mar 2, 2017
Please answer these questions before submitting your issue. Thanks!
What did you do?
Please consider the following program:
(https://play.golang.org/p/_YPsKUivic)
What did you expect to see?
What did you see instead?
Does this issue reproduce with the latest release (go1.8)?
yes
System details
The question here is whether map should be still considered usable after access with non-comparable element.
This issue originally came in the context of decoding python pickles and what to use - panics or reflect to detect non-comparable dict keys:
kisielk/og-rek#30 (comment) (and below).
Thanks beforehand,
Kirill
The text was updated successfully, but these errors were encountered: