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
You're right that the spec allows for such keys. (Actually, last time
I looked at the spec, it allows even nonsensical objects like arrays
and float64 NaNs to be map keys...)
Presently, the code only implements "string-like" keys, as that
preserves transparent JSON interoperability; there's a caveat to this
effect in the README.
This is something I'd consider fixing for a v2 revision, but probably
not as part of v1.
Hey, I was wondering, why does the code generator ignore my map in this struct?
As far as I know, the message pack spec allows such keys for maps
The text was updated successfully, but these errors were encountered: