)]}'
{
  "commit": "c1d608bb7e862c8d8b74ce7cfc042fa98e9d4792",
  "tree": "04b69115b984bfc35dc2dfa944334ce6127c4f3e",
  "parents": [
    "7fd85325c0b3b777888ca5ffc40d02d9dca37522",
    "b51d75e3a933cdce36627a0b531acb9521bef510"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Tue Jul 07 22:26:56 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Jul 07 22:26:56 2026 +0200"
  },
  "message": "Rollup merge of #158760 - kpeis695:fix/localkey-try-with-may-return, r\u003daapoalas\n\nClarify that `LocalKey::try_with` may return `AccessError`\n\nThe docs for `LocalKey::try_with` state that the function *will* return an `AccessError` when the key has been destroyed. That\u0027s not actually guaranteed:\n\n- `LocalKey::with` uses `try_with` internally and its docs explicitly acknowledge that it does not always panic when the destructor has run. If `try_with` really did detect every destroyed thread-local, `with` could always panic.\n- The top-level `LocalKey` docs already note: \"On all platforms it\u0027s possible for TLS to re-initialize other TLS slots during destruction.\"\n\nChange *will* to *may* to accurately reflect the best-effort nature of the destroyed-key check.\n\nCloses rust-lang/rust#157889\n\n@rustbot label +A-docs\n",
  "tree_diff": []
}