We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As seen in this rambly gist https://gist.github.com/Xaphiosis/2fa2b51b65e05c3addda1576f90a31ed
One way of getting around schematic unification disaster with the vcg method is via subset_refl. @lsf37 suggested we do this:
vcg
subset_refl
method svcg = rule conseqPre, vcg, rule order.refl
The question is whether we should look at anything else about this, deployment and the inevitable name bikeshed.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As seen in this rambly gist
https://gist.github.com/Xaphiosis/2fa2b51b65e05c3addda1576f90a31ed
One way of getting around schematic unification disaster with the
vcg
method is viasubset_refl
. @lsf37 suggested we do this:method svcg = rule conseqPre, vcg, rule order.refl
The question is whether we should look at anything else about this, deployment and the inevitable name bikeshed.
The text was updated successfully, but these errors were encountered: