-
Notifications
You must be signed in to change notification settings - Fork 8
Refinement of abstract features allows removal of classifier #2319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The problem (and the checking code) are not specific to abstract features. Here is
This example with data ports shows the problem:
|
The problem is also present with subcomponent refinement:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checking of abstract feature refinement allows the classifier to be removed. This is wrong, and allows violation of rule (L6):
Clearly an edge case has been missed, because verification does check that classifiers in the refinement are compatible with the original classifier.
I have the test package
Currently there are warnings when refinement changes to an incompatible classifier, but not when the classifier is removed alltogether.
The text was updated successfully, but these errors were encountered: