Scalaz Bind[Seq] typeclass

by

The collections library does backflips to accommodate subtyping: when you use map on a specific collection type (list, map, etc.), you’ll (usually) get the same type back. It manages this through the use of an extremely complex inheritance hierarchy together with type classes like CanBuildFrom. It gets the job done (at least arguably), but the complexity doesn’t feel very principled. It’s a mess. Lots of people hate it.

The complexity is generally pretty easy to avoid as a library user, but for a library designer it’s a nightmare. If I provide a monad instance for Seq, that means all of my users’ types get bumped up the hierarchy to Seq every type they use a monadic operation.

Scalaz folks tend not to like subtyping very much, anyway, so for the most part Scalaz stays around the leaves of the hierarchy—List, Vector, etc. You can see some discussion of this decision on the mailing list, for example.

When I first started using Scalaz I wrote a lot of utility code that tried to provide instances for Seq, etc. and make them usable with CanBuildFrom. Then I stopped, and now I tend to follow Scalaz in only ever using List, Vector, Map, and Set in my own code. If you’re committed to “Scalaz style”, you should do that as well (or even adopt Scalaz’s own IList, ISet, ==>>, etc.). You’re not going to find clear agreement on best practices more generally, though, and both approaches can be made to work, so you’ll just need to experiment to find which you prefer.

More Related Contents:

  1. How to convert A[B[C]] to B[A[C]] if A and B are monads?
  2. Turning A => M[B] into M[A => B]
  3. Using context bounds “negatively” to ensure type class instance is absent from scope
  4. Why isn’t Validation a Monad?
  5. Method parameters validation in Scala, with for comprehension and monads
  6. Confused with the for-comprehension to flatMap/Map transformation
  7. Update operations on a Scala Case Class
  8. Scala double definition (2 methods have the same type erasure)
  9. Advantages of F-bounded polymorphism over typeclass for return-current-type problem
  10. Why is this implicit ambiguity behaviour happening?
  11. Scalaz state monad examples
  12. How do I get an instance of the type class associated with a context bound?
  13. How to define partitioning of DataFrame?
  14. Case class equality in Apache Spark
  15. What is the difference between Scala’s case class and class?
  16. Dropping a nested column from Spark DataFrame
  17. sbt-assembly: deduplication found error
  18. Syntax sugar: _* for treating Seq as method parameters
  19. How to create a TypeTag manually?
  20. Weird behavior trying to convert case classes to heterogeneous lists recursively with Shapeless
  21. java.lang.NoClassDefFoundError: org/apache/spark/streaming/twitter/TwitterUtils$ while running TwitterPopularTags
  22. Forward References – why does this code compile?
  23. Spark: Add column to dataframe conditionally
  24. Why does Scala provide both multiple parameters lists and multiple parameters per list? [duplicate]
  25. How to clone a case class instance and change just one field in Scala?
  26. How to use third party libraries with Scala REPL?
  27. How do I pattern match arrays in Scala?
  28. How to prevent java.lang.OutOfMemoryError: PermGen space at Scala compilation?
  29. “return” and “try-catch-finally” block evaluation in scala
  30. Why does one select Scala type members with a hash instead of a dot?

Leave a Comment