-
Notifications
You must be signed in to change notification settings - Fork 21
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
aac_congruence #141
Comments
@aa755 I just maintain this project, and unfortunately have no plans to extend it with new tactics (but a PR implementing Someone who may be able to give a quick answer is @damien-pous, one of the original developers of the plugin/library. See also his website with contact info outside GitHub. |
Hi @aa755, |
Thanks Damien, I will leave this issue open since there is still the possibility of Just to double check also @aa755, you know about the |
if we had an |
Indeed aac_normalise does not work in hypotheses so far (and revert cannot help due to the way it's implemented). Meanwhile, here is a workaround:
We may also imagine variations, such as
|
The workaround is good enough for me. But
|
Indeed, the ordering of uninterpreted subterms (here variables) is unspecified. A patch should be feasible, but not straightforward. I'll try to have a look. |
The concrete problem I have now is that |
I've pushed a patch proposal in branch canonical-ordering (based on v8.19) @palmskog what would be the best way to provide a new version? (git/community/opam-wise...) I would be happy to test it against more users - my own libs using aac-tactics do not require any change. |
@damien-pous I think if the changes in the branch canonical-ordering fits the needs of @aa755, we should do two things:
I can take care of the merging to |
Thanks @palmskog ; would be great indeed if you could do the releasing/packaging ; I'll take care of porting to master. I would say the changes are worth a release (I was unhappy of the old behaviour quite a few times). |
Thanks for the fix. Indeed, the order now seems independent of the goal in my experiments. Also, the following proof which previously didn't work, does work now:
I am using your tactic notation ( |
Then it seems we all agree on a new release. @aa755 can I include your @damien-pous I assume I can take it from there and merge |
Sure. |
@palmskog, if you were not too fast, I've pushed the gcd instances in canonical-ordering, and I'm about to do it in canonical-ordering-master ;) |
@damien-pous thanks, I will likely do the release by tomorrow, so no chance of duplicated effort yet. |
ok, then I'll add lcm... (and stop there) |
Release with I think we keep this issue open to track any progress on aac_congruence that might happen, so I will remove "aac_normalise in" from the title. |
I recently found this library and found it to be very useful and wish I knew about it years ago.
Is it possible/easy to implement
aac_congruence
using the machinery defined here?For example, before calling congruence, one could put in some uniquish normal form expressions containing associative and commutative operators, similar to what
ring_simplify
does.If anyone has thought about writing
aac_congruence
oraac_normalize
I would love to know their thoughts and experiences.The text was updated successfully, but these errors were encountered: