)]}'
{
  "commit": "d7bb37872491c4bbdba02af3652f74a54aaa9333",
  "tree": "cf686866c418be76b50cee4ce74549de2d759019",
  "parents": [
    "5ad7363c398e503c2051ee10b4ca7307511129e0",
    "20c9f54404453c96e31d83f6587c999f21cbc6dc"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Wed Apr 22 19:18:27 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Apr 22 19:18:27 2026 +0200"
  },
  "message": "Rollup merge of #155133 - cuviper:duration_fp_docs, r\u003dthe8472\n\nDocument precision considerations of `Duration`-float methods\n\nA `Duration` is essentially a 94-bit value (64-bit sec and ~30-bit ns),\nso there\u0027s some inherent loss when converting to floating-point for\n`mul_f64` and `div_f64`. We could go to greater lengths to compute these\nwith more accuracy, like rust-lang/rust#150933 or rust-lang/rust#154107,\nbut it\u0027s not clear that it\u0027s worth the effort. The least we can do is\ndocument that some rounding is to be expected, which this commit does\nwith simple examples that only multiply or divide by `1.0`.\n\nThis also changes the `f32` methods to just forward to `f64`, so we keep\nmore of that duration precision, as the range is otherwise much more\nlimited there.\n",
  "tree_diff": []
}