)]}'
{
  "commit": "8d46f9cb5784b9eaea0c27fce151aeb341952c79",
  "tree": "fdf55226541bbddb5bf7ba89e60b70a243ed551b",
  "parents": [
    "1b364ae5d6e09dde5e0cc6b2087d7e8fd64730e1",
    "d2b1bb8a9b7a0a73b8da36d12798f4e848ed7171"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "matthias.krueger@famsik.de",
    "time": "Tue Apr 12 08:47:00 2022 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Apr 12 08:47:00 2022 +0200"
  },
  "message": "Rollup merge of #95920 - compiler-errors:cast-suggestion-span, r\u003doli-obk\n\nuse `Span::find_ancestor_inside` to get right span in CastCheck\n\nThis is a quick fix. This bad suggestion likely lives in other places... but thought it would be useful to fix all of the CastCheck ones first.\n\nLet me know if reviewer would prefer I add more tests for each of the diagnostics in CastCheck, or would like to do a more thorough review of other suggestions that use spans in typeck. I would also be open to further suggestions on how to better expose an API that gives us the \"best\" span for a diagnostic suggestion.\n\nFixed #95919\n",
  "tree_diff": []
}