-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
state monad using record as a state #48
Labels
Comments
Interesting. Coq shouldn't care about the record vs the pair, so a universe problem is possible, though I would highly doubt it, you aren't doing anything interesting with universes. Can you print the relevant universes? |
Changing definition of
Gives the following error:
|
vzaliva
added a commit
to vzaliva/helix
that referenced
this issue
Nov 13, 2018
vzaliva
added a commit
to vzaliva/helix
that referenced
this issue
Nov 13, 2018
This reverts commit 31277b9.
This seems to be fixed by making |
Is this still an issue? |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I am observing a strange error when using ExtLib. I am unsure if it is a bug or some sort of limitation, related to universes. In short, I've modified
examples/StateGame.v
ExtLib example, changing state type fromDefinition GameState: Type := (prod bool Z)
withRecord GameState : Type := mkGameState {on:bool; score:Z}.
. This lead to the following error message:At first glance
MonadState_state
instance should satisfy this constraint, but there is universe mismatch.The full example is enclosed below:
The text was updated successfully, but these errors were encountered: