been dying to make a post like this ngl i think it boils down to a couple things: * there's no way to set on a crate what targets are valid for it (fixable, implement this rfc: https://github.com/rust-lang/rfcs/pull/3759) * rust-analyzer is overly specialized towards single crate/single workspace usage and not the needs of a larger monorepo-type structure * because of the above two facts, rust-analyzer doesn't have enough info to properly condition/gate crates/architecture making fully-vertically-integrated rust needlessly painful --------------- There's other issues like: * no good way to tie probe-rs runner arguments to features/other cfg mechanisms, and upstream seems thoroughly uninterested in the usecase (https://github.com/rust-lang/cargo/issues/14314), shoving it off for proposals like this (https://github.com/rust-lang/cargo/issues/8170) where cargo maintainers over a year ago propose a pre-rfc that has been lowkey dead for two years I don't know if postprocessing compiled artifacts is really Cargo's domain though, so I wonder if we're going to get an explosion of handwritten xtasks/aliases for this sort of purpose (e.g. to repackage binaries for another build system or to run cargo in some sort of matrix)