Struct RefPrefixes 

pub struct RefPrefixes { /* private fields */ }

Available on crate features blocking-client or async-client only.

RefPrefixes are the set of prefixes that are sent to the server for filtering purposes.

These are communicated by sending zero or more ref-prefix values, and are documented in gitprotocol-v2.adoc#ls-refs.

These prefixes can be constructed from a set of RefSpec’s using RefPrefixes::from_refspecs.

Alternatively, they can be constructed using RefPrefixes::new and using RefPrefixes::extend to add new prefixes.

Implementations

impl RefPrefixes

pub fn new() -> RefPrefixes

Create an empty set of RefPrefixes.

pub fn from_refspecs<'a>( refspecs: impl IntoIterator<Item = &'a RefSpec>, ) -> Self

Convert a series of RefSpec’s into a set of RefPrefixes.

It attempts to expand each RefSpec into prefix references, e.g. refs/heads/, refs/remotes/, refs/namespaces/foo/, etc.

Inputs that aren’t fully qualified refs, like HEAD or main, are expanded in the same DWIM-style way that Git uses for ref-prefix generation, yielding prefixes like HEAD, refs/heads/main, and other rev-parse candidates.

Trait Implementations

impl Default for RefPrefixes

fn default() -> Self

Returns the “default value” for a type.

impl Extend<BString> for RefPrefixes

fn extend<T: IntoIterator<Item = BString>>(&mut self, iter: T)

Extends a collection with the contents of an iterator.

fn extend_one(&mut self, item: A)

🔬This is a nightly-only experimental API. (extend_one)

Extends a collection with exactly one element.

fn extend_reserve(&mut self, additional: usize)

🔬This is a nightly-only experimental API. (extend_one)

Reserves capacity in a collection for the given number of additional elements.