Stdlib and fusion evolution

Symbol renaming is indeed how modern languages / environments solve the issue:

Stdlib and fusion evolution

The solution is simply to rename the modules automatically. If you want a module to require a symbol such as `latest` as opposed to `1.0.0`, you can use a tag in your `requires` statement. The common alternative is to not specify a version for your requirement: `requires "foo"`, which suffers fr

Stdlib and fusion evolution

I'm not a stakeholder in nim, so I don't want to pollute the RFC, but I wanted to share that the "diamond" problem that arne and disruptek discussed is something that I've seen. What we did in that case is actually sort of similar to what Araq initially proposed. We had version folders (eg `v1`

Stdlib and fusion evolution

Maybe my thoughs about how to evolve Nim's stdlib and Fusion are not good enough for an RFC yet, but here is it anyway, Feedback appreciated, but please comment and vote on github and not here.