Future Proofing Compose

[mudgen]

A new design goal of Compose is to future proof it against major changes to the Solidity language which are coming.

1. The Solidity team has announced they are removing inheritance entirely from the language.

From the Solidity blog:

In addition to growing and expanding the language, we will also be removing or reworking some existing features. We are already certain that we will be removing inheritance entirely. Additional changes are less certain, but we are considering potentially replacing or reworking features like try/catch, libraries, function pointers, type conversion, and data locations.

Compose is already designed so it doesn't use inheritance.

The Solidity team is also planning to remove or replace Solidity libraries.

From a comment from a Solidity Compiler Team member:

We’ve long been dissatisfied with libraries and planning to drop them in the transition.

For future proofing Compose and making it simpler, I am thinking about removing Solidity libraries from Compose and instead using "Compose Libraries", which are simply Solidity files which declare constants, structs and free functions. I have done some testing on this and it works fine. I am interested in feedback on this change.