We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Cat a b
a
b
Context:
Greg Pfeil Jan 24, 2021 I'm all for kind-polymorphism, but if we don't have to do it this way, I'd much rather see a and b have the same kind.
Ziyang Liu Jan 24, 2021 I think we have to do it this way, in order to categorize
(name :: NameTy) -> ($fShowInt :: Show Int) This would be converted to Cat (NameTy :: *) (Show Int :: Constraint).
Cat (NameTy :: *) (Show Int :: Constraint)
Greg Pfeil Jan 27, 2021 Ok, yeah. But could you add a task to the "future CCC" epic about this, and reference it from the Cat newtype or somewhere?
Cat
(Extricated from https://kitty-hawk.atlassian.net/browse/SW-3538)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Context:
Greg Pfeil
Jan 24, 2021
I'm all for kind-polymorphism, but if we don't have to do it this way, I'd much rather see
a
andb
have the same kind.Ziyang Liu
Jan 24, 2021
I think we have to do it this way, in order to categorize
(name :: NameTy) -> ($fShowInt :: Show Int)
This would be converted to
Cat (NameTy :: *) (Show Int :: Constraint)
.Greg Pfeil
Jan 27, 2021
Ok, yeah. But could you add a task to the "future CCC" epic about this, and reference it from the
Cat
newtype or somewhere?(Extricated from https://kitty-hawk.atlassian.net/browse/SW-3538)
The text was updated successfully, but these errors were encountered: