`cargo gpu remove`

[Firestar99]

• cargo gpu remove --shader-crate ../shader-crate-template: should remove the rustc_codegen_spirv install of said shader crate
• cargo gpu remove --all should competely remove the entire cache dir, which would cleanup old installations by old cargo-gpu versions as well

Open Questions:

• remove or clean?
• cargo gpu remove <rust_gpu_version> We don't have a standardized way to declare a shader crate or a rust-gpu version. This would also be nice to have for installing
• Should we prompt the user about uninstalling toolchains as well? Note that two installs can use the same toolchain version. We could check every other install on whether the toolchain is used and prompt the user if noone is using it, which could be made easier by having some metadata file per install with the toolchain cached in it (among other things).

[tombh]

Great idea.

I lean slightly more to clean, but remove seems totally fine too. Though I must admit I'm not actually too familiar with the usecase of install, build has always just been enough for me. So from that perspective I'm not thinking in terms of removing as I didn't install anything. I'm sure if I knew what install was for I'd see it differently.

Regarding prompts for uninstalling toolchains, there is of course a non-zero possibility that the user already has need for said toolchain, in some other project completely unrelated to cargo-gpu. So I think prompting to uninstall would be polite.

[LegNeato]

I don't think we should use the term "shader" in APIs to refer to any code that runs on the GPU. GPGPU / compute generally uses "kernel". I'd suggest something that can cover both cases (I think the industry largely uses "device", which also isn't great)

[schell]

I prefer clean, just because that's what cargo uses. As far as shader vs kernel vs device, what if we use none of those and instead just (again) copy cargo with cargo gpu clean -p {path/to/crate.toml}?