get rid of ImmutableVector calls (WIP)
#5307
Open
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
The idea is to use "example vectors" with the desired internal representation whenever this is possible. Thus eventually only those (few) `ImmutableVector` calls will remain where GAP is expected to choose an appropriate internal representation. (And we will then see how this situation can be improved further.)
ThomasBreuer
added
kind: enhancement
|
This seems plausible to me |
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.
The idea is to use "example vectors" with the desired internal representation whenever this is possible.
Thus eventually only those (few)
ImmutableVectorcalls will remain where GAP is expected to choose an appropriate internal representation. (And we will then see how this situation can be improved further.)