[quote=“brson, post:130, topic:3316”] This situation should work fine with the exception that Cargo may sometimes invalidate some state when it detects the toolchain changing. I’m actually not clear on when this happens or what gets deleted.[/quote] I see. My experience was that a piece of code written on 1.8 that used to work (it depends on a bunch of crates) stopped building after SxS (yes, in general sense) installation of nightly.
I don’t know if it is possible to check after the fact whether this is coincidental (and, IDK, one of the cargos got updated or something) or rustup installation caused this. But based on your answer I should probably stop mixing MSI and rustup installation altogether. I’ll uninstall everything and try to reproduce my problem. Anything I should keep in mind looking for a repro?
Yes, this is what I was wondering about. Guidelines for the installation experience on Windows are convoluted and I get it why rarely installers do the right thing. What you’re describing (as much sense as it makes from the Rust point of view) defies some of the expectations. I’m not sure if this is the right thread for me to dissect what’s wrong but I’d be more than happy to write up what I think should change and why (based on platform guidelines) if you’re interested.
Either way, thanks for your reply, I’ll switch to rustup entirely and see how concurrent installations work for me without MSI.