On Tue, Jul 10, 2018 at 12:05 PM sebb wrote:
> What are the common use cases for this?
> Do they come from a particular field, and if so, where would you
> expect to find related code in Commons?
>
> Just a thought.
>
> If there are likely to be more classes in the same general area, maybe
> you
Am 10.07.2018 um 19:13 schrieb Gary Gregory:
> Yeah, I dislike *Util names as well, it's not only a co-out but an
> encouragement to make such classes dumping-grounds/kitchen-sinks.
>
> I was thinking [lang] or maybe [collections] but it's not a collection
> really.
As the implementation is
What are the common use cases for this?
Do they come from a particular field, and if so, where would you
expect to find related code in Commons?
Just a thought.
If there are likely to be more classes in the same general area, maybe
you have found a new component.
On 10 July 2018 at 18:13, Gary
Yeah, I dislike *Util names as well, it's not only a co-out but an
encouragement to make such classes dumping-grounds/kitchen-sinks.
I was thinking [lang] or maybe [collections] but it's not a collection
really.
Gary
On Tue, Jul 10, 2018 at 10:14 AM Rob Tompkins wrote:
> Wouldn’t this be an
Wouldn’t this be an argument for commons-util (specifically for extensions of
java.util)? Now, I whole heartedly disagree with naming things “XxxxUtils”
because I feel like the whole idea of naming a piece of a machine a utility is
a cop out and bad practice in semantics, so maybe this goes
Does anyone have any thoughts on where an OrderedObservable should live in
Commons if at all?
import java.util.ArrayList;
import java.util.List;
import java.util.concurrent.locks.Lock;
import java.util.concurrent.locks.ReadWriteLock;
import java.util.concurrent.locks.ReentrantReadWriteLock;
