Closed hseeberger closed 9 years ago
I would prefer that we stick to the Scala MultiMap interface where possible in order to minimise learning. We should be able to get and then put.
Can you please change if you agree?
That puts too much (hard) work into user space, I really want that (or a similar) function. If you strongly feel that sticking to the Scala MultiMap interface is needed (I don't understand why, because IMHO MultiMap is neither widely used in Scala nor available in Java, i.e. I don't consider it a standard), then we could probably go with filterNot
.
Scala's MultiMap
is our benchmark here I think. I would prefer to stick with methods that already exist. I also don't think that get
ting and then put
ting the values is too much work - unless we were doing it all of the time, which we're not.
Note that this is destined for Akka itself. We should be as idiomatic as possible.
Any thoughts @patriknw?
removeBinding
removes exactly the given element, yet sometimes that's not what you want, e.g. because you don't have/know the exact element, but only some discriminating property. ThereforeremoveBindings
is introduced which takes a predicate function determining which element(s) are to be removed.