-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
ParamSet might be too rich for some usecases #287
Comments
Do you really want to introduce a "sparse" parent class just to have a more tidy output? I don't know the OO lingo but introducing a class that is designed to have just one child seems to be overengeneering. I vote for close. |
No, I never said that, the "print" is only a summary. Just think about it like this:
that rule doesn't exist |
Does it fall into the category: "The user can do stupid things, and we don't care."? |
not really, as that API is publicly offered. I am not saying it is the most urgent issue, but i would maintain that this is not optimal.... |
Eg in bbotk we only use the PS to describe domain and codomains.
But we now have defaults in there, and also "values"
(which have both no place there)
maybe we should make that more configurable of have a hierarchies of classes
The text was updated successfully, but these errors were encountered: