core::path::Path

Hello Rustians!

I’m not proposing an API yet; I’m trying to understand whether this direction has already been considered or is architectually blocked.

The idea: Path feel like it could share a template/pattern-style abstraction: borrowed, allocation-free, usable in core, and separated from filesystem/OS behavior.

Questions:

• Is core::path impossible mainly because of platform path semantics / OsStr?
• Would a smaller abstraction, e.g. path-ish pattern parsing without IO, make sense?
• I am not 100% educated here and i am going to glady read any discussions i could not identify towards exactly this