aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorBruce Hill <bruce@bruce-hill.com>2026-02-21 13:07:09 -0500
committerBruce Hill <bruce@bruce-hill.com>2026-02-21 13:07:09 -0500
commitc0f624c9f6365d6c178a353e6f0974ed16f67339 (patch)
tree7aa6445f051dab9babb5497b8964b97ae26ed644 /docs
parent55d4731debd2d73e0f9d449c88ae9246f975f846 (diff)
Update docs
Diffstat (limited to 'docs')
-rw-r--r--docs/paths.md16
1 files changed, 0 insertions, 16 deletions
diff --git a/docs/paths.md b/docs/paths.md
index 810cb6df..c8a3d8c6 100644
--- a/docs/paths.md
+++ b/docs/paths.md
@@ -17,22 +17,6 @@ assert (/tmp) == (/tmp)
assert (~/path with/(parens) is/ok/) == (~/path with/(parens) is/ok/)
```
-### Interpolation
-
-Paths can contain interpolations using `$`, just like strings. However, there are
-certain values that _cannot_ be interpolated:
-
-- The literal string `.`
-- The literal string `..`
-- Any text that contains a forward slash (`/`)
-
-The intended use for path interpolation is to take user input which may or may
-not be trustworthy and interpret that value as a single path component name,
-i.e. the name of a directory or file. If a user were to supply a value like
-`..` or `foo/baz`, it would risk navigating into a directory other than
-intended. Paths can be created from text with slashes using
-`Path.from_text(text)` if you need to use arbitrary text as a file path.
-
# API
[API documentation](../api/paths.md)