Fix "id to index" bug #109
Merged
Conversation
This file contains 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
Otherwise we can mask the actual error.
- Don't set up tests to use default values (non-existing mapping value returns default value and can mask a problem) - Change some arbitrary index values to less conflicting numbers (for clarity).
They are dependable data structures and should be always in sync.
We shrink tokens array with tokens.length-- which makes tokens[lastTokenIndex] = 0 redundant.
mg6maciej
reviewed
Jun 24, 2018
| @@ -56,6 +56,7 @@ contract NFTokenEnumerable is | |||
| { | |||
| super._mint(_to, _tokenId); | |||
| tokens.push(_tokenId); | |||
| idToIndex[_tokenId] = tokens.length.sub(1); | |||
There was a problem hiding this comment.
push function returns new array length, so I tend to do:
uint length = tokens.push(_tokenId);
idToIndex[_tokenId] = length - 1;
Don't know if that's more gas efficient tho.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes: #106