Is there a good way to determine which (cargo) workspace a definition/file belongs to? All of the existing stuff seems tied to the 'vfs paths are opaque handles' idea which is good until you actually need the path.
I need it for #6332 so I can find the correct target directory to look for local documentation in.
@Zac Pullar-Strecker see how
handle_runnables work in