list-available/install don't seem to do bounds checking on Swift versions

[patricktcoakley]

Currently you are able to call list-available and install on arbitrary numbers like 0 or 400 without any indication that those are not real versions. It would be nice if it swiftly could at least keep track of actual releases to gate the args to actual toolchain releases before running any commands with a friendly error message.

[cmcgee1024]

Thanks, there could be some reasonable bounds to the selectors here, such as >1 and <30.

[patricktcoakley]

Would it make sense to cache the releases locally on bootstrap and gate them based on arch/platform for at least the minimum available versions and periodically update it?

[cmcgee1024]

It's a bit of a balancing act. The idea is to try and decouple swiftly from having too much knowledge that there would need to be a release of swiftly just to update its internal database, not feature/bug fixing to swiftly itself.

[patricktcoakley]

Yeah that makes sense as a design goal and changes how I might interpret some things, thanks for clarifying.