Repository navigation
Conversation
seidewitz
changed the title
seidewitz
changed the title
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.
This PR fixes an additional issue relative to the computation of the owned multiplicity of a type.
PR #809 corrected the implementation of
Type::getMultiplicity. However the implementation of the constraintvalidateTypeOwnedMultiplicitydoes not usegetMultiplicity-- it can't, becausegetMultiplicityalways returns zero or one value, and the constraint check needs to count all owned multiplicities to ensure there is no more than one. This means that the validation computation needs to be updated independently of the derivation computation. That is what is done in this PR.