Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Loopbreaker doesn't fill in ambiguous type applications #8

Open
isovector opened this issue Nov 1, 2019 · 2 comments · May be fixed by #9
Open

Loopbreaker doesn't fill in ambiguous type applications #8

isovector opened this issue Nov 1, 2019 · 2 comments · May be fixed by #9
Labels
bug Something isn't working high priority

Comments

@isovector
Copy link
Member 

src/Polysemy/Tagged.hs:1:1: error:
    • Could not deduce: Polysemy.Internal.Union.IndexOf
                          r (Polysemy.Internal.Union.Found r (Tagged k20 e))
                        ~ Tagged k20 e
        arising from a use of ‘retag’
      from the context: Member (Tagged k5 e) r
        bound by the type signature for:
                   retag__Loopbreaker_a1VWm :: forall k k3 (k4 :: k) (k5 :: k3)
                                                      (e :: (* -> *) -> * -> *)
                                                      (r :: [(* -> *) -> * -> *]) a.
                                               Member (Tagged k5 e) r =>
                                               Sem (Tagged k4 e : r) a -> Sem r a
        at src/Polysemy/Tagged.hs:1:1
      The type variable ‘k20’ is ambiguous
    • In the expression: retag
      In an equation for ‘retag__Loopbreaker_a1VWm’:
          retag__Loopbreaker_a1VWm = retag
    • Relevant bindings include
        retag__Loopbreaker :: Sem (Tagged k4 e : r) a -> Sem r a
          (bound at <no location info>)

for retag:

retag
    :: forall k1 k2 e r a
     . Member (Tagged k2 e) r
    => Sem (Tagged k1 e ': r) a
    -> Sem r a

This is a pretty high priority bug!
@isovector isovector added bug Something isn't working high priority labels Nov 1, 2019
@TheMatten TheMatten linked a pull request Nov 1, 2019 that will close this issue
Open
@isovector
Copy link
Member Author

Bump. What's the status of this?

@TheMatten
Copy link
Collaborator

I will try to look at this as soon as I will have enough time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working high priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix ambiguous loopbreakers polysemy-research/loopbreaker
2 participants
@isovector @TheMatten