Array functionality in Move #30
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
… test for Arrays contract
… move and added runtime test
…tion calls with element type
jessicalally
added
bug
mrRachar
approved these changes
Sep 16, 2020
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.
Changes
Array accesses
The Libra target had support for storing arrays as Libra vectors, but not for accessing or storing to them, as the original implementation had been broken by a Libra update. The code generated from Flint subscript expressions has now been updated to use the
Vector.borrow()andVector.borrow_mut()methods for array accesses, depending on whether the value should be mutated or not.Runtime functions for dynamic arrays
Three runtime functions,
Flint_array_remove(),Flint_array_insert()andFlint_array_length(), have been added to allow elements to be inserted into and removed from dynamic arrays.