Extendable bindings via separate packages
Re. qtah#16 (closed), it's useful to take some bindings and extend them via a separate package (e.g. for some custom classes that inherit from ones in the base library). Hoppy doesn't support this; everything that exists in an interface is both defined in and exported by the interface. Using a separate package is preferable to forking the base package.
Interfaces could declare parent interfaces that would be used for lookup, but not cause code to be generated. Some generated code might need to be shuffled from being with a parent class to instead being with a child class, but I don't see any major problems with this approach off the top of my head. Generator packages would then export their Interface
object publicly.
@effectfully, anything I missed here?