CoCo for non-unique CDRoleSymbols #21
Open
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 pull request adds:
Why?
The information of an association is distributed in several places in the symbol table. If an association is created that refers to its own class (self-loop) and does not define any explicit role identifiers, the identifier of the corresponding class is automatically used. Since these entries must be uniquely identified in the scope, the identifier must also be unique. The current procedure ignores role symbols if a symbol with the same identifier already exists in the scope.
The information in the scope as well as in the symbol table is lost!
(Several associations with automatically assigned role identifiers and cases with explicitly non-unique role identifiers behave in the same way)