Using explicit imports
Doug Simon
doug.simon at oracle.com
Tue Sep 15 08:19:46 UTC 2015
We recently changed the default policy for organizing imports to use explicit imports instead of on demand imports. The problems with on demand imports are described here:
https://bitbucket.org/allr/mx/commits/cf9105fe3b455e55bbe0f7227e0732963be4e104
Discussions on the pros & cons of this abound[1] but since we’re using IDEs that a) can organize imports and b) fold/hid them by default, all objections are sufficiently dealt with.
We did not apply an Organize Imports pass over all existing sources given how large (and potentially) disruptive such a change might be. However, as imports are made explicit future changesets will be a little noisier than usual until all sources are using explicit imports.
-Doug
[1] http://stackoverflow.com/questions/147454/why-is-using-a-wild-card-with-a-java-import-statement-bad
More information about the graal-dev
mailing list