Nix 2.26.3
Nix, the purely functional package manager; unstable internal interfaces
 
Loading...
Searching...
No Matches
nix::LookupPath::Prefix Struct Reference

Public Member Functions

 GENERATE_CMP (LookupPath::Prefix, me->s)
 
std::optional< std::string_view > suffixIfPotentialMatch (std::string_view path) const
 

Public Attributes

std::string s
 

Member Function Documentation

◆ suffixIfPotentialMatch()

std::optional< std::string_view > nix::LookupPath::Prefix::suffixIfPotentialMatch ( std::string_view path) const

If the path possibly matches this search path element, return the suffix that we should look for inside the resolved value of the element Note the double optionality in the name. While we might have a matching prefix, the suffix may not exist.

Member Data Documentation

◆ s

std::string nix::LookupPath::Prefix::s

Underlying string

Todo
Should we normalize this when constructing a LookupPath::Prefix?

The documentation for this struct was generated from the following files: