{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiah5oadu4wxbjbl27ectgs3igxre4anm7sd6ug26jxgtcqj3njutm",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mivd5wsjnn42"
  },
  "path": "/t/http-tower-hs-a-rust-tower-inspired-middleware-library-for-haskell/13892#post_11",
  "publishedAt": "2026-04-07T04:32:49.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I don’t think the `(|>)` question has a good answer at this point. It does smooth the on-ramp for people coming from pretty much any other FP language. I think defining it with a custom warning group is probably the best compromise position I’ve found so far, because then people coming to Haskell from other languages will search for it by reflex, find it, and then learn what we actually call the operator. But I don’t know who can best carry that responsibility, since it is redundant to have it fall to each package implementer.\n\nP.S.: `(&)` is defined in `base` already, in module `Data.Function`.",
  "title": "Http-tower-hs — A Rust Tower-inspired middleware library for Haskell"
}