Cargo workspaces and git sparse-checkout

Somewhat recent versions of git support a sparse-checkout powered by cone mode, and even scalar for optimizing git's large monorepo performance features.

The limitation of cone mode is that it works by selecting/excluding entire subfolders. This doesn't integrate super well with having a single Cargo workspace, since Cargo expects to be able to see all of the workspace members' manifests, and errors if member globs don't register any manifests (i.e. if the folder is excluded by cone-mode).

Are there any known tricks for letting cargo play better with sparse monorepo views? Or is this still mostly untrodden territory for now? (Using an x-like script to manage git cones is entirely reasonable, but I'd much prefer a solution that doesn't require dirtying or generating project manifests from another format.)

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.