mranderson
mranderson copied to clipboard
Handle deftype and java class with the same prefix in an import
example from here from claypoole
(:import
[com.climate.claypoole.impl
PriorityThreadpool
PriorityThreadpoolImpl]
[...])
this import prefixes two classes of claypoole itself. One of those classes is created with a deftype, the other one is created by a java class. MrAnderson prefixing deftype based classes in imports is a separate step from prefixing java class based classes in imports. The logic prefixing them is also different resulting in different prefixes. This means that inlining this library breaks now because the deftype prefixing "wins" for this import but this would render the java class based import wrong.
To fix either aline the two steps so they generate the same prefix or split this import into two so they can have different prefixes.