We often store semver as a String (eg in cw2) and parse it explicitly in the code, so that should be a decent work-around
Can you link the implementation of str_collect in another library for comparison?
Can you add a test case of your use case (adding semver ad dev-dependency is fine) so we see how this works in practice? Hard to add a feature unless the use-case is included.
I am currently working on an on-chain version management issue and wanted to store semver version requirements in my contracts.
Semver uses
ser.str_collect
for some of its values which is currently not supported (unreachable!()
).