Adjust depth calculation of map<K, V> type#12760
Open
alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
Open
Adjust depth calculation of map<K, V> type#12760alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
map<K, V> type#12760alexcrichton wants to merge 1 commit intobytecodealliance:mainfrom
Conversation
Previously it added 2 but this meant that it was out-of-sync with the fuzz test case generator which only accounted for 1 for each level of map. There's no need to have an extra layer for maps, so adjust the depth to add 1 instead of 2 which fixes the fuzz test case in question.
Member
Author
|
cc @yordis (to make you aware) |
yordis
approved these changes
Mar 11, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Previously it added 2 but this meant that it was out-of-sync with the fuzz test case generator which only accounted for 1 for each level of map. There's no need to have an extra layer for maps, so adjust the depth to add 1 instead of 2 which fixes the fuzz test case in question.