-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
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
debugging typeclass resolution in semantics #9
Comments
Even replacing the new case with |
You have to replace
with
|
This should be a simple "type mismatch" error of the form "expected cont, but found stmt", but due to typeclasses, it becomes quite undecipherable. I've got used to this and I debug it by commenting out all cases and then gradually add more cases until it breaks. I agree that this is unfortunate -- that's the price you pay for not eating bread and lentils every day... |
Thanks! |
As a part of an experiment I tried modeling continuations with explicit stacks. In ExprImp.v after defining
stmt
, the following codefails to check with an error
even if I replace the new case with
_
, I get a typelcass resolution error instead of afailed to infer something of type
which I normally use to debug mistyped code. There is probably just a typo or something equally stupid in this code, but the typeclass magic puts debugging it beyond my ability -- please help.The text was updated successfully, but these errors were encountered: