Sometimes imports of class or classes bound in a module
become undefined; there name is bound to nil.
Usually this can be solved be recompiling the
class referenced.
For the time being I don't know the exact reason.
Best theory so far: The class builder does not handle renaming classes correctly wrt. environments.
Fix: Recompile the class being referenced.
This also happens with names bound in the very same module they are used in. I suppose this is due to the missing undefined handling.
Just for the record: Behavior>>#literalScannedAs:notifying: writes to Undeclared
I suspect this issue is connected to #16.
One simple cause is the promotion of an alias interface to a real one, that misses an export, which in turn the importing module uses to import that symbol.