{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicdqekuljphjf4qo5bnk3u7h76pg2bhptlsplouemdps5ufrs6hym",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mnfip3q2uvn2"
  },
  "path": "/t/possibility-of-a-global-time-source-for-wasm-targets/24370#post_2",
  "publishedAt": "2026-06-03T15:21:23.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "source code"
  ],
  "textContent": "Having this option would be very nice for `wasm32-unknown-unknown` users, including myself, but the problem I see with it is that it _only_ makes sense for `wasm32-unknown-unknown` users, given the status quo. `wasm32-unknown-unknown` having a stubbed-out `std` is an unusual situation; other targets generally either have a non-panicking `std` (even if, say, all `fs` operations _return_ errors) or don’t have `std` at all. But perhaps there are other targets that can’t natively implement `Instant` that I don’t know of (the source code would take more work to make an exhaustive list out of) or new odd platforms will come along.\n\nIn any case, I don’t think this is a _bad_ feature; I’m just unsure whether it has enough use cases for the Rust maintainers to be willing to add this complexity.",
  "title": "Possibility of a \"global time source\" for wasm targets"
}