Georgi Krastev
Georgi Krastev
Also why do we have all of these which are slightly different? It's really unmanageable: * `Expr::schema_name` * `Expr::canonical_name` * `physical_name`
Maybe we can just use the `schema_name` for `physical_name`? It sounds like a bug if they are different: https://github.com/apache/datafusion/pull/11977
> Therefore, individual backport PRs like this one are (though obviously well intentioned, of course — thank you!) aren't as helpful as one might think and probably won't be merged....
They are also similar to `partition` :smile: How about: | Scalaz | collections | |-|-| | `splitWith` | `partitionAll` | | `splitBy` | `partitionGroup` | | `selectSplit` | `partitionFilter` |
Yes, I meant `span`... I keep confusing these two methods and for the life of me I can't remember which is which. If `split` is chosen then it should do...
Do you mean `cats-testkit` or `cats-testkit-scalatest`? Kittens migrated to MUnit.
But both `Functor` and `Contravariant` are `Invariant` which composes. Why do we need special instances for them?
Interesting, that might be an issue with Shapeless 3 or even Scala 3
Looks like Scala 3 behaviour ```scala scala> summon[Mirror.Of[MyString]] -- [E172] Type Error: ---------------------------------------------------------- 1 |summon[Mirror.Of[MyString]] | ^ |No given instance of type scala.deriving.Mirror.Of[MyString] was found for parameter x of method...
Looks like people tried and it didn't work: https://github.com/scala/scala3/issues/7000