Hi, No, sorry, but you still miss the point.
The thing Kevin tries to explain is that the collection methods are far more flexible, because they can select the “next best available” type if the “best available” type just doesn't exist. This occurs in “the real world” (BitSet, String, ...) and that's why it is solved in the standard library instead of pushing the work to the developers. To my knowledge no other language out there goes to this great lengths to make this work as developers expect (most accurate return types, collections integrating with non-collection types, ...), but I will be happy to get corrected. So the reasons for all the CanBuildFrom stuff are very pragmatic and practical ones. If those “Scala type theorists” would really live in some academic ivory tower (as some people suggest) the “simple” signatures would certainly be “good enough”. Hope this helps a bit. Thanks and bye, Simon -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/Hp7iVuKd630J. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
