commit 504a235bed25579766685f0ec4130812bae922f6
parent 72356abe447ac95f9bc663bae0d8e394c8949ce6
Author: Sebastian <sebastian@sebsite.pw>
Date: Sat, 9 Dec 2023 21:14:29 -0500
path: mention fs::resolve in README
Signed-off-by: Sebastian <sebastian@sebsite.pw>
Diffstat:
1 file changed, 4 insertions(+), 0 deletions(-)
diff --git a/path/README b/path/README
@@ -15,6 +15,10 @@ normalized, which is to say that it will not include any of the following:
Assuming that [[SEP]] is '/', "/usr//bin/../bin/./hare/" becomes "/usr/bin/hare"
and "../../foo/bar" is unchanged.
+Different [[fs::fs]] implementations may have different rules for normalizing
+paths. For use-cases in which this is relevant, [[fs::resolve]] should be used
+instead.
+
The buffer object includes an array of length [[MAX]], which can be somewhat
large; on Linux it's 4095 bytes. You can allocate this on the stack in most
cases, but you may prefer to allocate it elsewhere depending on your needs.
