Find a way to label and maintain a "maturity" level for packages (experimental... -> audited)
gbotrel opened this issue · 1 comments
gbotrel commented
Should be consistent with gnark repo.
Some packages are highly experimental, obviously unsecured and subject to drastic changes, while some other are time-tested / audited.
An initial idea (cc @ivokub ) was to force the use of build tags for experimental features + some automated go:generate script to update a table in the README.md + godoc. A draw back is refactoring / ide integration will suffer a bit from that.
gbotrel commented
see also discussion here: golang/go#34409