Open epage opened 6 years ago
That would be fine. What name do you suggest?
PathArc was chosen because it mimicks PathBuf and gives the user immediate feedback that it is cheap to copy.
Some possible names:
PathNonAbs
PathAny
PathMaybe
(I don't like any of these names personally, but thought it might get some ideas flowing)
Why not just Path
? Its what you get when you strip the suffix. I assume the rest are Arc
s too and are missing the suffix.
Mainly because I don't want to conflict with std::path::Path
This was first discussed on reddit.
For "low level" APIs, having
Arc
in the name makes sense. If this is a higher level API meant to focus more on the Python type of users, we should abstract that implementation detail and leave it out of the name