Struct LooseWorkspace 

pub struct LooseWorkspace {
    pub root: PathBuf,
    pub cwd: PathBuf,
    pub current_package: Option<String>,
}

Discovered cargo workspace context.

Fields

root: PathBuf

Directory containing the [workspace] Cargo.toml.

cwd: PathBuf

Directory we were invoked from. May or may not be a member crate — the user might run from the workspace root itself.

current_package: Option<String>

[package] name from <cwd>/Cargo.toml, when the cwd is a crate. None means the user ran from a non-crate dir (e.g. workspace root with no top-level package); we’ll skip the -p <pkg> filter.

Implementations

impl LooseWorkspace

pub fn discover(cwd: PathBuf) -> Result<Self>

Discover the workspace context starting from cwd. Errors only on the unrecoverable case (no enclosing cargo workspace at all).

pub fn cargo_invocation_dir(&self) -> &Path

Return the dir to invoke cargo from. We prefer the current package’s dir when present so its [package.metadata.*] settings take effect; otherwise fall back to the workspace root.

pub fn detect_profile_feature(&self) -> Result<String>

Sanity-check the cwd’s Cargo.toml exposes a profile feature that activates anchor-v2-testing/profile. Returns the discovered feature name (almost always "profile") or a hard error if we can’t find anything that would trigger trace writing.

Two acceptable shapes:

1. profile = ["anchor-v2-testing/profile"] — the convention.
2. Any feature that contains "anchor-v2-testing/profile" — for workspaces that name it differently (e.g. tracing).

pub fn check_dev_dep(&self) -> Result<()>

Sanity-check that anchor-v2-testing is actually a dev-dependency. Without it, --features profile would fail with an opaque cargo error; we’d rather flag this up front.