-
-
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 Nes and Nec equivalents of Nel functions #2543
Adding Nes and Nec equivalents of Nel functions #2543
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2543 +/- ##
==========================================
+ Coverage 95.17% 95.18% +<.01%
==========================================
Files 359 359
Lines 6553 6561 +8
Branches 278 278
==========================================
+ Hits 6237 6245 +8
Misses 316 316
Continue to review full report at Codecov.
|
#2475 merged :) |
@kubukoz Thanks! I'll clean my PR up |
@kubukoz Hi! I think this is ready for review |
Do we need 2 +1's from reviewers with write access to merge? Not sure how that works, thanks! |
Thanks @calvinbrown085! Sorry but I have to ask: are we confident in |
Hrm, that is a good point. I guess I assumed |
I was referring to NonEmptySet, but I didn't realize there was
NonEmptyStream too. I don't think we should have these short names in that
case, as NES is ambiguous.
…On Fri, Oct 5, 2018, 15:32 Calvin Brown ***@***.***> wrote:
Hrm, that is a good point. I guess I assumed NonEmptySet but I can see
either way! Looking at this comment by @kubukoz
<https://github.com/kubukoz> #2475 (comment)
<#2475 (comment)> it
seems like he was referring to NonEmptySet but he might have to clarify
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2543 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA2npOuqH6bxQembah6Idb8ulek-nHcNks5uh19-gaJpZM4XAlyF>
.
|
That's unfortunate, we do already have some precedent with |
addresses #2539
We might need to merge #2475 first because our changes are going to overlap each other, happy to merge the previous PR then fix conflicts in my branch.