⟨/⟩ AT Protocol Record Source
at://did:plc:pi6woz4d47bkuws673w2il2r/site.standard.document/3mnu34he7iw62
← Back to post
{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif2z4n24rzdcb7desv5txjmfaroqky4aklufj5u37orjvpr4sw6ju",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mnu34he7ic62"
  },
  "path": "/t/is-there-a-way-to-get-a-oschar-literal-more-conveniently-than-osp-head/14206#post_10",
  "publishedAt": "2026-06-09T09:05:55.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I’d stick with `isExtensionOf` here. `OsChar` isn’t really a Unicode character anyway—it’s closer to a unit of the underlying OS string encoding. For filepath extensions, working at the `OsString`/filepath level is usually cleaner and avoids encoding-related surprises.",
  "title": "Is there a way to get a OsChar literal more conveniently than osp + head"
}