Many (imported) libraries expect the user to inherit from a base class that is required for certain functionality or it makes life easier by providing default behavior in the base class
Patch base and subclass:
Profit from inheritance design patters in patched libraries
Current problems
Inheritance itself is already supported by the type system, but cannot be expressed in patches
NodeBrowser doesn't display inherited members
Workaround with a wrapper comes with the problem of being a new type that cannot be connected to operations of the wrapped class. So it needs two outputs, the state output, and the wrapped class output -> Ugly/unclear patches
Member operations of the base class output the base class, even if connected to a subclass
There are two scenarios to this:
Inherit from third party class:
Patch base and subclass:
Current problems