)]}'
{
  "commit": "1d3d73ee5ad8f4ce3230e2cee29d9fef587df638",
  "tree": "fe98e3aba45012d3638a11230e9eb7f85ec15f0f",
  "parents": [
    "f6f7ddddd56bea7bb87e74f021ed9f89e41f5a38",
    "d60f7800ef5fb3996a8c74f57b9932ab913448af"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Wed Dec 03 13:05:13 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Dec 03 13:05:13 2025 +0100"
  },
  "message": "Rollup merge of #149244 - spastorino:fix-mem-drop-rustdoc, r\u003dChrisDenton\n\nFix std::mem::drop rustdoc misleading statement\n\nThis is a bit misleading, we were discussing this with our Rust team and some people could think that the compiler does some special magic for this specific function and that\u0027s not true or well the compiler does something special but for every function.\nThe reality according to my understanding is that this is a normal function that takes ownership of the given value and as with every other function mir building injects Drop Terminators , drop elaboration refines this and then we would insert the corresponding drop glue, then potentially calling Drop::drop.\n\nNot sure if it would be best to remove the sentence as this PR does or explaining something along the lines of the previous text.\n",
  "tree_diff": []
}