{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreierqgl4nkckct4dzxzi3c5kn5mhes3cj6lsop64kfqdvql75smsem",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mltldsb2jq32"
  },
  "path": "/t/instant-past-value-constant/24297#post_11",
  "publishedAt": "2026-05-14T17:37:52.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "toc:\n\n> Granted that logic is still iffy for `Instant::MIN` on devices which zero their timers to boot up (but that's probably fine).\n\nThis is not a niche thing -- `CLOCK_MONOTONIC` is counted from boot time on Linux and probably many others. But for the 1 second delay in this example, I agree it's probably fine.\n\nAnother quirk of `MIN` is that this could be **far** in the past, e.g. on Unix targets that use `tv_sec: i64`, versus Windows with unsigned `Instant(Duration)`. So the range of `Instant::MIN.elapsed()` could be wildly different!",
  "title": "`Instant::PAST_VALUE` constant?"
}