diff options
author | Stefan Zeiger <szeiger@novocode.com> | 2016-07-06 19:42:57 +0200 |
---|---|---|
committer | Stefan Zeiger <szeiger@novocode.com> | 2016-07-07 15:08:07 +0200 |
commit | 7e933d5b5a4c1c8795b74e67e2148c6fc4ca19a6 (patch) | |
tree | 6a7309dfe74e0b996700774dd0abae2c37cc4255 /test/files/presentation | |
parent | 6612ba010b0e70c53550d1e47141c8dc89a55f23 (diff) | |
download | scala-7e933d5b5a4c1c8795b74e67e2148c6fc4ca19a6.tar.gz scala-7e933d5b5a4c1c8795b74e67e2148c6fc4ca19a6.tar.bz2 scala-7e933d5b5a4c1c8795b74e67e2148c6fc4ca19a6.zip |
SI-6947 Better type parameter names for Map classes
Type parameter names are currently assigned pretty much alphabetically
without any meaning. This change renames all key parameters in Map
classes from `A` to `K` and all value parameters from `B` to `V` to
make them more meaningful. Derived names are renamed accordingly (e.g.
`V1` instead of `B1` for an upper bound on `V`, `W` instead of `C` for
a new value type).
As a side-effect this solves the documentation problem in SI-6947. Due
to using `B` both as a type parameter for `foldLeft[B]` in
`GenTraversableOnce[A]` and in `Map[A, B]` which extends
`GenTraversableOnce[(A, B)]`, the signature of `Map.foldLeft` was
rendered in scaladoc as
def foldLeft[B](z: B)(op: (B, (A, B)) ⇒ B): B
Now you get an unambiguous version:
def foldLeft[B](z: B)(op: (B, (K, V)) ⇒ B): B
Diffstat (limited to 'test/files/presentation')
0 files changed, 0 insertions, 0 deletions