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
Pierre Roux
Iris
Commits
48b5fd55
Commit
48b5fd55
authored
7 years ago
by
Robbert Krebbers
Browse files
Options
Downloads
Patches
Plain Diff
Mention Coq issue 6583.
parent
2eb91537
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
-9
5 additions, 9 deletions
theories/proofmode/tactics.v
with
5 additions
and
9 deletions
theories/proofmode/tactics.v
+
5
−
9
View file @
48b5fd55
...
@@ -383,15 +383,11 @@ Notation "( H $! x1 .. xn 'with' pat )" :=
...
@@ -383,15 +383,11 @@ Notation "( H $! x1 .. xn 'with' pat )" :=
Notation
"( H 'with' pat )"
:=
(
ITrm
H
hnil
pat
)
(
at
level
0
)
.
Notation
"( H 'with' pat )"
:=
(
ITrm
H
hnil
pat
)
(
at
level
0
)
.
(*
(*
There is some hacky stuff going on here (most probably there is a Coq bug).
There is some hacky stuff going on here: because of Coq bug #6583, unresolved
Holes -- like unresolved type class instances -- in the argument `xs` are
type classes in the arguments `xs` are resolved at arbitrary moments. Tactics
resolved at arbitrary moments. It seems that tactics like `apply`, `split` and
like `apply`, `split` and `eexists` wrongly trigger type class search to resolve
`eexists` trigger type class search to resolve these holes. To avoid TC being
these holes. To avoid TC being triggered too eagerly, this tactic uses `refine`
triggered too eagerly, this tactic uses `refine` at various places instead of
at most places instead of `apply`.
`apply`.
TODO: Investigate what really is going on. Is there a related to Cog bug #4969?
When should holes in an `open_constr` be resolved?
*)
*)
Local
Tactic
Notation
"iSpecializeArgs"
constr
(
H
)
open_constr
(
xs
)
:=
Local
Tactic
Notation
"iSpecializeArgs"
constr
(
H
)
open_constr
(
xs
)
:=
let
rec
go
xs
:=
let
rec
go
xs
:=
...
...
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