-
Notifications
You must be signed in to change notification settings - Fork 9
Fix/solverprecision #9
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
base: master
Are you sure you want to change the base?
Conversation
syaskovets
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which use case problem does it solve? In this implementation the point expression and the other operand T d either have the same type, or the type of the operand is implicitly converted to double (which works for all base types). I don't see why it has to be compared with float here
The Dcpse class uses point expressions which ambiguously match for the division operator to both cases when the type is Float, resulting in compilation failure when compiling float versions. |
|
Could you please provide a reproducible example? I would like to understand the issue and fix it for all point_expression_op's. For now it seems adding |
Compiling the above results in: |
Allowing for petsc to work in float and double both