Open matthiaskrgr opened 1 year ago
That should be fairly easy, the main problem being that we'd never clean up when a toolchain gets uninstalled.
The folder logic is here:
AFAIK rustup sets an env var with the active toolchain, that we could simply take into account here.
the main problem being that we'd never clean up when a toolchain gets uninstalled.
Could we pick a miri folder inside the toolchain? Won't work for distro based miri, but once that's a thing we'll figure sth out.
Or maybe ship the miri sysroot as part of the miri component?
Or maybe ship the miri sysroot as part of the miri component?
That's not possible as we'd have to ship a miri sysroot per target
Not sure if messing with rustup's toolchain folder is a good idea. Also that won't work on nix (where the toolchain folder is read-only).
would be nice if miri was able to have separate caches for its std build for
cargo +master miri...
andcargo +nightly miri...
for example, to avoid frequent rebuilds when experimenting with different toolchains at the same time.