Allow FList
to store MultiPack
entries
#902
Merged
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 PR adds a functionality mentioned in the comments of #900.
Description of changes
In this PR, we modify the interface of
FList
to store and processMultiPack
entries. Currently, these are mainly used by theMultiPackGroup
entry to store group members. The way this happens is that for MultiPack entries, we store them as a tuple of thetid
of the entry and thetid
of theDataPack
the entry is associated with.Possible influences of this PR.
We can now store
MultiPack
entries inFList
now, something that was not not possible earlier.Test Conducted
Describe what test cases are included for the PR.