Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Iris
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Gaëtan Gilbert
Iris
Commits
2abfa296
Commit
2abfa296
authored
7 years ago
by
Ralf Jung
Browse files
Options
Downloads
Patches
Plain Diff
explain why we use typeclasses eauto
parent
74e4d637
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
theories/proofmode/tactics.v
+5
-0
5 additions, 0 deletions
theories/proofmode/tactics.v
with
5 additions
and
0 deletions
theories/proofmode/tactics.v
+
5
−
0
View file @
2abfa296
...
...
@@ -629,6 +629,11 @@ Tactic Notation "iIntoValid" open_constr(t) :=
let
e'
:=
eval
unfold
e
in
e
in
clear
e
;
go
(
t
e'
)
|
_
=>
let
tT'
:=
eval
cbv
zeta
in
tT
in
eapply
(
as_valid_1
tT'
);
(* Doing [apply _] here fails because that will try to solve all evars
whose type is a typeclass, in dependency order (according to Matthieu).
If one fails, it aborts. However, we rely on progress on the main goal
([AsValid ...]) to unify some of these evars and hence enable progress
elsewhere. With [typeclasses eauto], that seems to work better. *)
[
solve
[
typeclasses
eauto
with
typeclass_instances
]
||
fail
"iPoseProof: not a BI assertion"
|
exact
t
]
end
in
go
t
.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment