-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Unintuitive class behaviour #185
Comments
Reading through https://pythonhosted.org/uncertainties/tech_guide.html#python-classes-for-variables-and-functions-with-uncertainty AffineScalarFunc -> UExpression
Variable -> UFloat
ufloat() -> UFloat(), ie the class' __init__ With documentation instructing users to use |
The technical guide states
UFloat
is the recommended class to use forisinstance
checks.UFloat
to beUFloat
, notAffineScalarFunc
ufloat
to be aUFloat
, or at least aAffineScalarFunc
since that's what I imported.Variable
to anAffineScalarFunc
. Given the name ufloat, I expect these objects to behave similarly to a float and return the same type as the original object.It would be more intuitiave for the class the user sees to be called UFloat.
Could a single class be exposed to the user, rather than
Variable
andAffineScalarFunc
?The text was updated successfully, but these errors were encountered: