Hey,
thanks for your feedback. It's interesting to see that there seem to be two
opposing opinions:
Some try to avoid static imports as much as possible, while others use them
if it makes the code more fluent.
I found the Matt's comment especially useful, for pointing out, that we (as
developers
FYI, the Project Lambda Streams code and JSR-310 in JDK 1.8 are both
written with static imports in mind. Moreover, with support for static
methods in interfaces being added, this is likely to increase as a
pattern. Those facts may or may not affect decisions in commons.
Stephen
On 4 February
Hi,
we had a little discussion in BeanUtils2, regarding static imports (see
below). To increase visibility and get some more feedback, I'm forwarding
this to [ALL]
We haven't decided yet how to handle static imports. To form some rules,
we'd like to hear what others think about static imports
On Mon, Feb 4, 2013 at 4:32 PM, Benedikt Ritter brit...@apache.org wrote:
Hi,
we had a little discussion in BeanUtils2, regarding static imports (see
below). To increase visibility and get some more feedback, I'm forwarding
this to [ALL]
We haven't decided yet how to handle static imports.
Another common use is with junit to import assertEquals and such.
On Mon, Feb 4, 2013 at 4:41 PM, Gary Gregory garydgreg...@gmail.com wrote:
On Mon, Feb 4, 2013 at 4:32 PM, Benedikt Ritter brit...@apache.org
wrote:
...
We haven't decided yet how to handle static imports. To form some
I would say that in general the Commons libraries favor *creating* APIs
such that intent reads most fluently by *not* using static imports. I
would venture to say that given the examples of when static imports might
be desirable, a good rule of thumb wrt *use* of static imports would again
be
