With non-unique keys, later stored entries are not taken into account anymore #963
Labels
documentation
solution: proposed fix
a fix for the issue has been proposed and waits for confirmation
Milestone
While updating to 3.1.0, I noticed that the behavior of the library is not consistent with the documentation anymore for objects with non-unique names (also discussed in issue #375).
Whereas it will now be treated equally as
{"key": 2}
instead.I bissected to the commit 85c7680 replacing
operator[]
withemplace
to insert an object, which will not update an already existing object in themap
.I actually don't need this "feature" anymore, so not sure if it's best to fix the code for consistency or update the corresponding documentation.
The text was updated successfully, but these errors were encountered: