Call out what happens to duplicate keys in Map.map/2 in the docs #11360
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
We should probably document what happens when Map.map/2 produces collisions in the keys. Given that the current implementation uses :maps.from_list/2, I opted to just use the same verbiage as Map.new/2.
| 💚 💙 💜 💛 ❤️ |
josevalim pushed a commit that referenced this pull request Nov 3, 2021
| How does |
| Good find @garazdawi! |
josevalim added a commit that referenced this pull request Nov 15, 2021
This reverts commit 6074846.
| Oh geez, I totally misunderstood. 🤦♂️ |
josevalim added a commit that referenced this pull request Nov 16, 2021
This reverts commit 6074846.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Per the discussion in #11239, this adds a note that if the function you pass to
Map.map/2produces duplicate keys, only the last one will be kept.