diff options
author | Vlad Ureche <vlad.ureche@gmail.com> | 2012-07-02 20:42:38 +0200 |
---|---|---|
committer | Vlad Ureche <vlad.ureche@gmail.com> | 2012-07-16 23:41:44 +0200 |
commit | 891769fae541513d68ce7a8e84b7213472c333c9 (patch) | |
tree | 63815332d3636198229cc7da7bdd7307e04d89bb /build.xml | |
parent | 8779ade6f57ef15a04babf9715bc7ca4cbbdc425 (diff) | |
download | scala-891769fae541513d68ce7a8e84b7213472c333c9.tar.gz scala-891769fae541513d68ce7a8e84b7213472c333c9.tar.bz2 scala-891769fae541513d68ce7a8e84b7213472c333c9.zip |
Scaladoc: workaround for untypical Map usecases
SI-3448 partial fix:
This enables a workaround for the fact that Map takes two type params
while $Coll takes only one. But it doesn't fix the problem though,
as there's one more piece missing from the puzzle - we need to adjust
the `Coll`s in {immutable, mutable, concurrent}.Map to something that
makes sense for the usecase. And that's not possible. But I'm
committing this nevertheless, maybe other projects can benefit from it.
And for SI-3448, the solution lies in automatic usecase generation,
whenever that will be ready.
Diffstat (limited to 'build.xml')
0 files changed, 0 insertions, 0 deletions