Type parameter of minBy[B](f: ((A, B))? B)(implicit cmp: Ordering[B]): (A, B)?

You analysis is correct, it should be renamed as C, or something else. The problem is that scaladoc is simply replacing the A in the definition in TraversableLike with a Tuple (A, B) because it's a map. This is the definition from TraversableLike.

You analysis is correct, it should be renamed as C, or something else. The problem is that scaladoc is simply replacing the A in the definition in TraversableLike with a Tuple (A, B) because it's a map. This is the definition from TraversableLike: def minBy B (f: (A)?

B)(implicit cmp: OrderingB): A because it's a map, scaladoc replaces the (A) with a tuple (A, B). Def minBy B (f: (A, B)? B)(implicit cmp: OrderingB): (A, B) which as you observe, isn't actually the correct signature.

This is a known issue, scaladoc does not disambiguate between same-named type parameters. Vote it up or submit a patch!

Ah, okay, I was wrong about that source remark. The minBy method is declared in GenTraversableOnce, then defined in TraversableOnce - and both don't know about B. So it is really a scaladoc issue.

Thank you both. – Theodosius Dec 6 '11 at 10:29.

It seems like the software that builds the documentation has simply failed to rename the B variable from the trait's definition of minBy, thus causing a name clash. Your analysis seems correct. To use the terminology from lambda calculus, I'd say that the software failed to alpha-convert.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.