We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packmap keeps duplicate keys (and entries) behavior might be considered undefined, though its probably better to copy C# implementation
[ { "type": "Map", "value": [ { "key": { "type": "Integer", "value": "1" }, "value": { "type": "Integer", "value": "1" } }, { "key": { "type": "Integer", "value": "1" }, "value": { "type": "Integer", "value": "1" } } ] } ]
C# results:
[ { "type": "Map", "value": [ { "key": { "type": "Integer", "value": "1" }, "value": { "type": "Integer", "value": "1" } } ] } ]
./bin/neo-go vm
loadbase64 ERERERK+
run
The text was updated successfully, but these errors were encountered:
Wow, a really unexpected bug! Sure, it should be aligned with C# implementation. They use an ordered dictionary for the internal Map item implementation, so the bug is legit. https://github.com/neo-project/neo/blob/3f2f78c1fcf71ea51f2c40c3a0e67062ac390aed/src/Neo.VM/JumpTable/JumpTable.Compound.cs#L45 https://github.com/neo-project/neo/blob/3f2f78c1fcf71ea51f2c40c3a0e67062ac390aed/src/Neo.VM/Types/Map.cs#L63
Sorry, something went wrong.
And it's a map, it can't have duplicate keys, one key --- one value.
No branches or pull requests
Current Behavior
packmap keeps duplicate keys (and entries)
behavior might be considered undefined, though its probably better to copy C# implementation
Expected Behavior
C# results:
Possible Solution
Steps to Reproduce
./bin/neo-go vm
loadbase64 ERERERK+
run
Your Environment
The text was updated successfully, but these errors were encountered: