Defining implicit view-bounds on Scala traits

后端 未结 3 1051
长情又很酷
长情又很酷 2021-02-13 10:28

I\'m doing an exercise to implement a functional binary-search-tree in Scala, following a similar pattern that I\'ve seen used in Haskell. I have a structure that looks somethin

相关标签:
3条回答
  • 2021-02-13 11:02

    The problem is that view bounds as well as context bounds are just syntactic sugar for specific types of implicit parameters. When applied to a type parameter of a generic class (as opposed to when applied to a generic method), these implicits are added to the constructor of the class. Because traits have no constructor (or rather, only have a single parameterless constructor), there is nowhere to pass these implicit parameters and thus context bounds and view bounds are illegal on generic traits. The simplest solution would be to turn TreeNode into an abstract class.:

    abstract class TreeNode[A <% Ordered[A]]
    

    Note that as advised by Ben James, using a context bound with an Ordering is usually better than a view bound with an Ordered (it is more general). However the problem is still the same: won't work on a trait.

    If turning TreeNode into a class is not practical (say you need to mix it at various places in the type hierarchy), you can define an abstract method in TreeNode that will provide the implicit value (of type Ordered[A]) and have all the classes that extend it define it. This unfortunately more verbose and explicit, but you can't do much better in this case:

    trait TreeNode[A] {
      implicit protected def toOrdered: A => Ordered[A]
    }
    
    case class Branch[A<%Ordered[A]](value: A, left: TreeNode[A], right: TreeNode[A]) extends TreeNode[A] { 
       protected def toOrdered = implicitly[A => Ordered[A]]
    }
    
    case class Leaf[A<%Ordered[A]]() extends TreeNode[A] { 
        protected def toOrdered = implicitly[A => Ordered[A]]
    }
    

    Note that for a more concise definition, you could equivalently define Leaf like this:

    case class Leaf[A](implicit protected val toOrdered: A => Ordered[A]) extends TreeNode[A]
    
    0 讨论(0)
  • 2021-02-13 11:17

    @ben-james's answer is great, I would like improve it a bit to avoid redundant vals in classes.

    The idea is to define implicit constructor parameter name the same as it is defined in trait that holds implicit value.

    The idea is to avoid this line:

    val evidence = ev
    

    Here is a complete example (gist)

    trait PrettyPrinted[A] extends (A => String)
    
    object PrettyPrinted {
      def apply[A](f: A => String): PrettyPrinted[A] = f(_)
    }
    
    trait Printable[A] {
      implicit def printer: PrettyPrinted[A]
    }
    
    // implicit parameter name is important
    case class Person(name: String, age: Int)
                     (implicit val printer: PrettyPrinted[Person])
      extends Printable[Person]
    
    object Person {
      implicit val printer: PrettyPrinted[Person] =
        PrettyPrinted { p =>
          s"Person[name = ${p.name}, age = ${p.age}]"
        }
    }
    
    // works also with regular classes
    class Car(val name: String)
             (implicit val printer: PrettyPrinted[Car])
      extends Printable[Car]
    
    object Car {
      implicit val printer: PrettyPrinted[Car] =
        PrettyPrinted { c =>
          s"Car[name = ${c.name}]"
        }
    }
    
    0 讨论(0)
  • 2021-02-13 11:23

    You could provide the "evidence" that A is Ordered by requiring an abstract member of type Ordered[A] on the trait:

    trait TreeNode[A] {
      implicit val evidence: Ordered[A]
    }
    

    You would then be forced to provide this in any concrete subtypes, this proving that A is Ordered:

    case class Leaf[A](value: A)(implicit ev: Ordered[A]) extends TreeNode[A] {
      val evidence = ev
    }
    

    You might instead want to constrain A to a type which has an implicit Ordering[A] - this is not an inheritance relationship; it is more like a haskell typeclass. But the implementation in terms of the above technique would be the same.

    0 讨论(0)
提交回复
热议问题