-
-
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
Order to Ordering conversion #1665
Comments
By the way if this is added via |
Yeah, adding it to `cats.implicits._` seems like it would be what most
users want.
…On Sat, May 13, 2017 at 05:45 Cody Allen ***@***.***> wrote:
By the way if this is added via cats.implicits._, then #1659
<#1659> is a relevant change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1665 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEJdvWJkBl94FW7Toz3_Swi4IeD0_Nvks5r5dAWgaJpZM4NaG39>
.
|
I'll go ahead tonight and put up the fixed PR. |
Resolved by #1670. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #1646 there's a discussion about how there's a conversion from
Order
toOrdering
but that it won't actually be picked up where an implicitOrdering
instance is expected.It sounds like the general consensus is that we should make it so that after you've imported
cats.implicits._
you pick up this functionality.It may not make a lot of sense to expose this as an implicit in the
Order
companion object, because it won't be found there during an implicit search for anOrdering
instance, and having it there will probably result in ambiguous implicits if someone imports bothcats.implicits._
andOrder._
. However, we may not want to make this incompatible change to cats-kernel. @johnynek do you have thoughts on this?The text was updated successfully, but these errors were encountered: