{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih3h7l7ub4ppg3ntbjz36yxqqcezpymc2jyblh2is5jpqxacqkmve",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mk4csgnbrbw2"
  },
  "path": "/t/add-an-implementation-for-the-default-trait-for-std-controlflow/24191#post_4",
  "publishedAt": "2026-04-22T18:25:32.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "steffahn:\n\n> I see `ControlFlow` as \"like `Result` with _without_ the semantic extra assumptions `Result` comes with\"\n\nThis is absolutely 100% the intent of the type, yup.\n\nIt replaces code that was extremely confusing because it was using `Err` for \"success\" because having `?` short-circuit that was helpful. This is also why while `Result` has `map` and `map_err` but `ControlFlow` has `map_break` and `map_continue`: Neither variant is \"preferred\" over the other.",
  "title": "Add an implementation for the Default trait for std::ops::ControlFlow"
}