Asked by tycooperaow in CryptoDevs discord -solidity-dev channel
My assumption is that Vyper is still Beta (see the update on the compiler(s) below) and that with no inheritance, OpenZeppelin Contracts implementation on Vyper would be different.
Vyper resources (wiki post, please add/edit):
Agree with your thoughts, Andy. Also, and as far as I understand, Vyper has no code reusability mechanism (except for interfaces) which makes it a poor choice for a library of reusable smart contracts.
I could see that preset opionated contracts of ERC standard tokens could potentially be created in Vyper.
Something like the equivalent of the preset contracts in OpenZeppelin contracts: https://docs.openzeppelin.com/contracts/3.x/api/presets
@vasa-develop is working on a Vyper library.
Agreed. Even if it’s not possible to have a library like
@openzeppelin/contracts (due to lack of inheritance), developers still need reference contracts. So for now, a repository with community audited code would be helpful.