-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Adding WriterT Monoid #1014
Adding WriterT Monoid #1014
Conversation
After using in our application code further I'm seeing similar behaviour that @ceedubs is seeing for In particular I seem to have some trouble resolving the
|
I've checked in |
Is this SI-2712? |
I compiled against @milessabin proposed fix for SI-2712 and it A simplified repro,
|
In particular, this helps implicit resolution when `F` is `Id`.
@yilinwei thanks a lot for getting the ball rolling on this and identifying implicit resolution issues! I've submitted a PR to your branch that helps with the case of I'm not sure what to do about the |
Use instance hierarchy for WriterT group instances
Current coverage is 81.99%
@@ master #1014 diff @@
==========================================
Files 215 215
Lines 2704 2710 +6
Methods 2639 2647 +8
Messages 0 0
Branches 60 58 -2
==========================================
+ Hits 2217 2222 +5
- Misses 487 488 +1
Partials 0 0
|
I think we can leave the Xor use case for now - I'm not really familiar with codecov.io - what does the check mean and is there anything I should be doing? |
👍 lgtm. I don't entirely understand what's going on with the code coverage report. I think something weird is happening because of the separation of the |
👍 |
Adding WriterT Monoid as referenced in #1012.
It's also come to my attention that it's one of the subtasks in #620.