Work with file paths by text only.

In the Windows operating system, absolute paths may either start with a drive letter followed by a colon, or an UNC path prefix (\\), or an extended drive letter prefix (\\?\X:). Therefore, this crate provides a FlexPath that is based on a variant ([FlexPathVariant]), which you don't need to always specify. This variant indicates whether to interpret Windows absolute paths or not.

There are two FlexPathVariant variants currently:

• Common
• Windows

The constant FlexPathVariant::native() is one of these variants based on the target platform. For the Windows operating system, it is always Windows. For other platforms, it's always Common.

Example

use hydroperx_path::FlexPath;

assert_eq!("a", FlexPath::new_common("a/b").resolve("..").to_string());
assert_eq!("a", FlexPath::new_common("a/b/..").to_string());
assert_eq!("a/b/c/d/e", FlexPath::from_n_common(["a/b", "c/d", "e/f", ".."]).to_string());
assert_eq!("../../c/d", FlexPath::new_common("/a/b").relative("/c/d"));

hydroperx::path

Work with textual file paths, including relativity and resolution. Features:

• Variant: FlexPath methods consider absolute paths according to the path's FlexPathVariant. Two variants are supported: Common and Windows. The native variant can be deduced directly through _native suffixed methods.
• Normalization: normalize paths with the normalize_path() function, whether they exist or not (does not solve for symlinks and real letter case).

Requirements:

• The Rust standard library (std).

Example

use hydroperx_path::FlexPath;

assert_eq!("a", FlexPath::new_common("a/b").resolve("..").to_string());
assert_eq!("a", FlexPath::new_common("a/b/..").to_string());
assert_eq!("a/b/c/d/e", FlexPath::from_n_common(["a/b", "c/d", "e/f", ".."]).to_string());
assert_eq!("../../c/d", FlexPath::new_common("/a/b").relative("/c/d"))