Rename composition_property struct#932
Merged
MFraters merged 1 commit intoMar 31, 2026
Merged
Conversation
Pull Request Test Coverage Report for Build 23797376669Details
💛 - Coveralls |
|
MFraters
approved these changes
Mar 31, 2026
Member
MFraters
left a comment
There was a problem hiding this comment.
Thanks!
In general I don't like abbreviations like cp_output and cp_parsed. I think it is clearer when it is written out. In this case the scope where those abbreviations are being used is very small and clear, so I think in this case it is fine.
This file contains hidden or 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
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.
Following #926, renamed Parameters::composition_property (a struct indicating all properties of one composition) to distinguish from composition_properties (a map linking composition indices with their composition_property). All renamed variables are internal so previous results and tests should not be affected.
I have also tested making composition_properties a vector and did not find it a good idea. Since users are allowed to assign arbitrary composition indices (as long as they are unique), handling this cleanly is more cumbersome with a vector.
The feature parser will come shortly after.