DRY class inheritance in Motoko

I’ve run into this elsewhere: How are awaits handled that don't call an async function? - #17 by skilesare

The big issue being the awaits and potential hidden logic in the async functions that make these kind of things less safe to do when trying to wrap the source actor function with an enhanced function(ie trying to derive from dip20 and wrap it in an standardizing function). State can be committed out from under a dev with little understanding of the underlying code.

That being said…I’d love this feature and it would make the creation and Integration of utility actors much easier.