Add support polykind for Quote from Prim.TypeError#4142
Add support polykind for Quote from Prim.TypeError#4142rhendric merged 3 commits intopurescript:masterfrom
Quote from Prim.TypeError#4142Conversation
|
|
||
| A custom type error occurred while solving type class constraints: | ||
|
|
||
| Don't want to show Just @Type String because. |
There was a problem hiding this comment.
I think we should probably strip the kind annotations out here (the @Type bit).
There was a problem hiding this comment.
We still want to show them when --verbose-errors is set, right?
There was a problem hiding this comment.
If we already decided on a strategy of showing kind annotations when verbose errors is on, then applying that same strategy here sounds good. I can’t remember whether that should be happening anyway; do the tests run with verbose errors on?
There was a problem hiding this comment.
As far as I can tell, in the only places we're currently erasing kind annotations in error messages, we do so conditional on verbose errors being off. I believe the tests don't run with verbose errors, which maybe makes testing that the erasure is conditional on verbosity difficult.
Also, it seems there are plenty of other places where we don't do this and perhaps should (just grep for @ in tests/**/*.out), which maybe makes dumping this request on this PR a little unfair? I agree that it should be done, but maybe we should clean this up holistically (and figure out how to test it robustly) in a separate PR.
There was a problem hiding this comment.
Ok, yes, that makes sense.
There was a problem hiding this comment.
We don’t strip them in the error “trace” to aid debugging.
Hiding kind annotations can happen separately.
|
@xgrommx, could you please:
When that's squared away, we can merge! |
|
@rhendric what do u mean about rebase? |
|
@xgrommx he means |
|
@xgrommx Any updates on this? |
|
@JordanMartinez sorry I was in vacation. |
|
It's ok? |
|
@xgrommx Ah, no worries about that. I hope you enjoyed your vacation! Your example above is fetching data from Below is what I get when I run $ git remote -v
origin git@github.com:JordanMartinez/purescript.git (fetch)
origin git@github.com:JordanMartinez/purescript.git (push)
rh git@github.com:rhendric/purescript.git (fetch)
rh git@github.com:rhendric/purescript.git (push)
upstream https://github.com/purescript/purescript.git (fetch)
upstream https://github.com/purescript/purescript.git (push) |
|
Rather than rebasing on |
Previously
Quoteworking only with kindType. Now it will be support any kindFor Example
Will be produce