Various changes in libs

[MathisGD]

• Harmonize libraries naming with Lib suffix
• Put WAD definition outside of FixedPointMathLib, because it should be easily accessible from the outside (it will not clash because you are not forced to import it)
• Harmonize comments in FixedPointMathLib
• Harmonize fixed point arithmetics functions naming

[pakim249CAL]

For SafeTransferLib, there are a few options I can suggest that would solve this issue:

• We can simply replace our IERC20 with solmate's ERC20
• We can make another lib function that accepts an address or an IERC20, and does the conversion and calls the appropriate SafeTransferLib library functions. Maybe in a special lib named something like "SafeTransferAddressLib"
• We can just make an internal function to do this.

[Rubilmax]

What's the issue with using solmate's ERC20?
You can also rename the import

[QGarchery]

What do you think about Errors not being a library ? It would place all constants at top level. Reasons for doing so:

• shorter names
• no real risk of name clash (constants in all caps)
• ErrorsLib feels weird

[Rubilmax]

What do you think about Errors not being a library ? It would place all constants at top level. Reasons for doing so:

• shorter names
• no real risk of name clash (constants in all caps)
• ErrorsLib feels weird

Features lost:

• backward solidity compatibility (anyway it's already lost with types being defined at the top level)
• errors can be all imported using the short import statement instead of having a multi-line import statement for each of the errors used within a file

I'm ok with both solutions

[QGarchery]

Btw, it would be nice to have errors and events handled in the same way. We could even put the errors in IBlue.sol (it works).

For instance, I don't see why events can be imported with a solidity version >= 0.5.0, but errors cannot (currently)

[Rubilmax]

Let's archive morpho-utils at this point