I know macOS support came late to swiftly, but what support we do have now seems at odds with how the platform actually works. For instance, when swiftly is first installed, all command line swift invocations are broken, as it doesn't integrate with the tools installed with Xcode. Additionally, when you install toolchains through swiftly, that integration never returns. Really swiftly should allow usage of both.
So are these limitations inherent to swiftly, or just not implemented yet?
Wasn’t that recently resolved per this comment on GitHub?
Once it's in a release I can give it a try. However, I shouldn't have to specify use xcode when there are no other toolchains involved. By default, nothing should be broken upon installation.
Why would you install swiftly if no other toolchains are involved in the first place? If you’re interested only in Xcode toolchains swiftly is of no use to you, as far as I understand.
Much the same reason as anyone else: I want to easily install and try various toolchains from swift.org. macOS' only difference is that it has separate toolchains from Xcode that must be used to ship code. So it would be nice if swiftly didn't break that workflow by default, and wasn't broken if I delete all the old toolchains. It would also be nice if it naturally integrated with the versions of Swift installed by Xcode, alongside toolchain versions, so I could automatically switch as I build different projects.
IMO GitHub issues are more appropriate to track these requests than Swift Forums.