-
Notifications
You must be signed in to change notification settings - Fork 538
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
Implemented very silly workaround for #807 #849
Conversation
@@ -169,8 +169,8 @@ sealed abstract class Resource[+F[_], +A] { | |||
* | |||
**/ | |||
def parZip[G[x] >: F[x]: Sync: Parallel, B]( | |||
that: Resource[G, B] | |||
): Resource[G, (A, B)] = { | |||
that: Resource[G[?], B] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this one is necessary, btw.
Seems like it works 🤷 |
Could you explain what it does, I'm slightly at a loss :) |
@SystemFw It seems like, when it comes to variant constructors, |
Weird. Should we use the new kind projector syntax with `*` ?
…On Wed, Apr 29, 2020, 16:05 Daniel Spiewak ***@***.***> wrote:
@SystemFw <https://github.com/SystemFw> It seems like, when it comes to
variant constructors, F and [x]F[x] are not *entirely* equal inside of
scalac. So what my workaround does is I replaced F with [x]F[x] in the
type signatures. This is invisible 99.9% of the time, but in this case it
appears to entirely fix the inference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3I33R2F7BMC3GP3RD5MWDRPA64DANCNFSM4MTMH26Q>
.
|
@SystemFw I was going to implement that change across the whole project soon. For now, I just went with what was already there. |
Ah! Makes sense
…On Wed, Apr 29, 2020, 18:42 Daniel Spiewak ***@***.***> wrote:
@SystemFw <https://github.com/SystemFw> I was going to implement that
change across the whole project soon. For now, I just went with what was
already there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3I33SZKWBWKBRS5LFAJRDRPBRJZANCNFSM4MTMH26Q>
.
|
Would also appreciate a look from @neko-kai. I think this works around the issue. It's a little annoying, but I wasn't able to find anything more elegant, and the nice thing is that it doesn't touch binary compatibility. I believe it should also be fully source-compatible with all existing call-sites that weren't already broken.
Fixes #807 (I think)