In the rare case the class name (and all of its package components) of an
import statement was the same as the package for another import, the
first import would get merged into the second incorrectly. This was a
function of how imports were represented internally.
For instance, the import ca.example.Class would get merged into the
import ca.example.Class.OtherClass.
To address this, the import statement structure was reworked to handle
such cases.
In the rare case the class name (and all of its package components) of an import statement was the same as the package for another import, the first import would get merged into the second incorrectly. This was a function of how imports were represented internally.
For instance, the import
ca.example.Classwould get merged into the importca.example.Class.OtherClass.To address this, the import statement structure was reworked to handle such cases.
Fixes #15 Fixes #5