Expand description
Shared traversal-validation logic for the zenops-safe-relative-path
family.
Both the runtime SafeRelativePath type and the compile-time
srpath! proc macro need to agree on what counts as a “safe”
relative path. The rule lives here so neither side can drift from the
other. Application code should depend on zenops-safe-relative-path
instead of pulling this crate in directly — this exists as the seam
between the runtime crate and the proc-macro crate.
Functions§
- is_
safe_ relative_ path - Returns
trueifpathcontains no..components.