-
Notifications
You must be signed in to change notification settings - Fork 34
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
What is the distinction between Dictionary and ControlledDictionary? #469
Comments
I believe you are correct. I believe ControlledDictionary should be a subclass of Dictionary (and ControlledDictionaryEntry a subclass of DictionaryEntry) as the difference is them is simply a narrowing constraint on the set of values allowed in the types:key property of ControlledDictionaryEntry class. |
I will implement subclassing as a bugfix. |
Once PR 418 is merged, I'll file a PR to fix this. |
No effects were observed on Make-managed files. References: * #469 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Implementation is being tested in PR 476. |
No effects were observed on Make-managed files. References: * ucoProject/UCO#469 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#469 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#469 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#469 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
While implementing Issue 430, I observed
types:Dictionary
andtypes:ControlledDictionary
are both parentless classes. I could not see a reason thatControlledDictionary
would not be a subclass ofDictionary
.The practical difference I see between the two is the corresponding entry class, where
ControlledDictionaryEntry
verbally describes a constraint on a set of values. There is no implementation of such a constraint.Is the intent for
ControlledDictionary
to be a disjoint class fromDictionary
, and likewise for theirEntry
classes?Coordination
develop
The text was updated successfully, but these errors were encountered: