Platform-independent lexical path with / separators.Roots are stored separately so POSIX normalization cannot collapse UNC'sleading // or mistake C:/ for a relative path. Absolute paths clamp ..at the root; relative paths retain leading ... An empty relative portiondenotes the root, or . without a root. Components retain literal backslashes.This type does not access the filesystem or resolve symlinks.See Linux filename rulesand path resolution.
Render the normalized path. Relative paths with a drive-like first componentretain ./ to distinguish component names from drive roots.A POSIX component can contain :, and . denotes the current directory:filename rules,path resolution.
Parse uniform syntax with / separators, preserving literal backslashes.Roots use /, C:/, C:, or //server/share/; drive letters are ASCII.Three or more leading slashes denote a POSIX root.Use from_windows to parse Windows separators explicitly.
Append the relative portion of another normalized path, preserving thispath's root. The other path's root is ignored. Both operands are alreadyparsed and normalized.
Resolve another normalized path against this explicit base without readingthe host environment. Absolute POSIX, drive, and UNC paths replace the base;ordinary relative paths are joined to it. The result can remain relative.A drive-relative path is joined to a base on the same drive, comparing driveletters without case sensitivity and preserving the base's root.Raises ResolveError::DriveBaseRequired when that drive base is unavailable.