A representation of a path-like string with optional row and column numbers.
Matching values example: te, test.rs:22, te:22:5, test.c(22), test.c(22,5)etc.
In memory, this is identical to Path. On non-Windows conversions to this type are no-ops. On
windows, these conversions sanitize UNC paths by removing the \\\\?\\ prefix.
Case-insensitive ASCII comparison of a path component to a literal
folder name. macOS and Windows use case-insensitive filesystems by
default, so a path like .ZED/settings.json resolves to the same
inode as the lowercase form. A case-sensitive == check would miss
those and let a malicious settings author bypass classifiers with
unusual casing. Callers should restrict name to ASCII; for ASCII
inputs eq_ignore_ascii_case is safe and stable across platforms.
Whether path sits under (or exactly equals) any of the given subtree
grants. As with insert_subtree, containment is purely lexical, so
callers should pass normalized paths.