Closed GoogleCodeExporter closed 9 years ago
FWIW, precedent is that these overloads would not go into a separate
SortedMultisets utility class, but would stay in Multisets. (See e.g. Maps,
which keeps its SortedMap and BiMap overloads in the same place.)
Original comment by lowas...@google.com
on 13 Mar 2014 at 9:11
That makes sense. I didn't realize that was a common paradigm in the library. I
guess the user will have to force which overloaded version to use.
Original comment by amojo...@gmail.com
on 13 Mar 2014 at 9:44
The user shouldn't need to force anything. As long as the types of the two
arguments to the method are both SortedMultiset (or a subtype of it), the
overload that takes two SortedMultisets will be selected as the most specific
overload by the compiler.
Original comment by cgdecker@google.com
on 13 Mar 2014 at 9:53
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:09
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:17
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:07
Original issue reported on code.google.com by
amojo...@gmail.com
on 13 Mar 2014 at 9:09