-
Notifications
You must be signed in to change notification settings - Fork 12
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
Term normalization for .quad
function?
#145
Comments
We shouldn't overthink. I don't want to discourage good discussions, do keep coming up with corner cases. However, many issues are full of "fake Suggestion: let's assume that fake |
While this issue is related to the
.equals
function, it actually exists outside the scope of the other discussions we've had. This one might be addressed by amending the definition of the.quad
function itself, but right now there is asymmetry in the naive implementation:Most importantly, without specifying some needs for normalizing arguments passed to
.quad
(as it is now), we will see different behavior, i.e., inconsistencies in the results of.equals
, between implementations that normalize terms passed to.quad
and those that don't.I understand that the parameter type is specified as
Term
to the.quad
function, but I think it's important to at least consider and discuss these circumstances. Possibly related to #104 and #137The text was updated successfully, but these errors were encountered: