{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigbr7xyet3xayg5g2vzwntmlz6dreljg7dkxbq3u4sn3rizrtscpu",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mlehpbi3wr72"
  },
  "path": "/t/core-path/24233#post_1",
  "publishedAt": "2026-05-08T19:10:01.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Hello Rustians!\n\nI’m not proposing an API yet; I’m trying to understand whether this direction has already been considered or is architectually blocked.\n\nThe idea: `Path` feel like it could share a template/pattern-style abstraction: borrowed, allocation-free, usable in `core`, and separated from filesystem/OS behavior.\n\nQuestions:\n\n  * Is `core::path` impossible mainly because of platform path semantics / OsStr?\n  * Would a smaller abstraction, e.g. path-ish pattern parsing without IO, make sense?\n  * I am not 100% educated here and i am going to glady read any discussions i could not identify towards exactly this\n\n",
  "title": "core::path::Path"
}