forked from coq/coq
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ltac2: named type variables can't be defined
If we want to build doc from code we need the annotated types to be accurate. Notice how in the stdlib we had a couple less than accurate type annotations. This differs from how ocaml does things but TBH I strongly dislike how ocaml does things in this case.
- Loading branch information
1 parent
a41fd86
commit 69bcb60
Showing
4 changed files
with
46 additions
and
19 deletions.
There are no files selected for viewing
6 changes: 6 additions & 0 deletions
6
doc/changelog/06-Ltac2-language/18118-ltac2-rigid-typ-var.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
- **Changed:** | ||
explicit type variables are rigid, such that annotations like | ||
`Ltac2 id (x:'a) := ...` ensure that `id` will be polymorphic. | ||
Previously for instance `Ltac2 bad_id (x:'a) : 'b := x.` would be accepted | ||
(`#18118 <https://github.com/coq/coq/pull/18118>`_, | ||
by Gaëtan Gilbert). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters