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
where the code tries to use the map[string]interface{} as a key when the child is a slice.
When reading the comments in the code:
// FLAG_IGNORE_SLICE_ORDER causes Equal to ignore slice order so that
// []int{1, 2} and []int{2, 1} are equal. Only slices of primitive scalars
// like numbers and strings are supported. Slices of complex types,
// like []T where T is a struct, are undefined because Equal does not
// recurse into the slice value when this flag is enabled.
This states it is unsupported to use it with this type of data. I was wondering if it is possible to add this feature in the future.
At least this ticket could save others some time when they do a web search for the cause of the error and did not read the documentation ;)
The text was updated successfully, but these errors were encountered:
Please see the example 5) from this playground: https://go.dev/play/p/M-VZFkXte9T
With FLAG_IGNORE_SLICE_ORDER set, it causes a panic.
It happens at:
where the code tries to use the map[string]interface{} as a key when the child is a slice.
When reading the comments in the code:
This states it is unsupported to use it with this type of data. I was wondering if it is possible to add this feature in the future.
At least this ticket could save others some time when they do a web search for the cause of the error and did not read the documentation ;)
The text was updated successfully, but these errors were encountered: