Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
The second should raise an error. Our dictionaries do not preserve insertion order so we don't even know which one is the duplicate.
For the first case where it's unambiguous I'd find it more convenient to allow this and automatically convert the key to a string, just like Association>> jsonWriteOn: does (there is an argument for removing this method though, because unlike all other methods it does not by itself produce valid JSON)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.