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
Add dfs flag for typeclasses eauto
#14693
Add dfs flag for typeclasses eauto
#14693
Conversation
Should I update the documentation to talk about the new syntax? |
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.
Please update as described. The wording is a suggestion.
doc/changelog/04-tactics/14693-alizter+typeclasses-eauto-dfs-flag.rst
Outdated
Show resolved
Hide resolved
74731fe
to
3e69ce5
Compare
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.
Better, a few more nits.
b24f7d2
to
8376bfb
Compare
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.
2 more small tweaks.
8376bfb
to
9fba97f
Compare
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.
The doc looks good
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.
It's great to include a test case, but ideally, this test case would check that the two modes actually do something different (right now, you can only manually inspect the debug output). The idea would be to choose goals which fail when run with the wrong mode (dfs
or bfs
) and succeed with the other. Then you could insert Fail 1: typeclasses eauto ...
to assert this.
Otherwise, LGTM 😄
@Zimmi48 They shouldn't succeed on the wrong modes in the test case. The classes and values were picked carefully so that they fail when the wrong mode is given. Should I add a comment to the case making this clearer? |
That's what I expected when looking at the test case, so I wanted to suggest inserting the appropriate |
Oh, that's not supposed to happen. Let me take a look. |
@Zimmi48 I'm confused, how are you testing this on 8.13? Could you give me something that doesn't work? I am unable to break it. |
We allow passing a dfs flag to `typeclasses eauto`. Previously only bfs could be passed which meant that if the global enviornment had dfs set, there was no way to do `typeclasses eauto` using dfs locally.
We test `typeclasses eauto dfs` and `typeclasses eauto bfs` in both global dfs or bfs environments.
Co-authored-by: Jim Fehrle <jim.fehrle@gmail.com>
9fba97f
to
ca35997
Compare
In the test, |
I was testing without the new syntax. But indeed, I hadn't really read the test precisely and I had missed that the |
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.
I'll merge this PR tomorrow.
@coqbot merge now |
Fixes / closes #13859
make -f Makefile.make doc_gram_rsts
.