Enum Honoured 

pub enum Honoured {
    By {
        file: &'static str,
        code: &'static str,
    },
    ByDependency {
        krate: &'static str,
        item: &'static str,
    },
    Vacuously(&'static str),
}

Where the code that honours a capability lives.

Every entry in every advertisement table carries one of these, and tests/advertisement.rs reads them: the named file, with its comments stripped, must contain the named code. Comments are stripped because contains("push-options") is satisfied by the paragraph explaining push-options two lines above the call — a guard that a doc comment can satisfy is a guard that survives the deletion of the thing it guards.

Variants

By

Read by code in file containing the substring code.

file is relative to the workspace root.

Fields

file: &'static str

Workspace-relative path.

code: &'static str

A substring of the line that reads it, e.g. peer.has("atomic").

ByDependency

Read by a public item of a crate gunnar depends on, not by a file in this tree.

This variant exists because the other one could not tell the truth here. ofs-delta’s obligation is discharged by gunnar-pack, which lived at ../edda/crates/gunnar-pack and was cited as a workspace-relative PATH — a path that only resolves on a machine with an edda checkout beside gunnar. From a fresh clone (and, since 2026-09-09, from every clone, since the crate is a crates.io dependency) the citation named a file that is not there, and the guard failed for the absence of a sibling rather than for anything about gunnar.

A path was the wrong shape for the claim anyway. What is being asserted is that a named ITEM exists in a named CRATE, and the compiler can assert that exactly — advertisement.rs carries a use of every item cited this way, so the guard is a build error rather than a substring search, and it holds whether the crate resolves from the registry or from a patched sibling checkout.

Fields

krate: &'static str

The crate as cargo names it, e.g. gunnar-pack.

item: &'static str

The public item that does the work, e.g. index_thin_pack.

Vacuously(&'static str)

There is nothing to do, and here is the argument for why.

The reason is a sentence, not a marker: this variant is the escape hatch and it has to cost something to use. Today exactly three capabilities use it, and each says what makes it vacuous rather than unimplemented.

Trait Implementations

impl Clone for Honoured

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for Honoured

impl Debug for Honoured

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for Honoured

impl PartialEq for Honoured

fn eq(&self, other: &Self) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for Honoured