)]}'
{
  "commit": "77a5cb0194bbe911d8862dbece4ee6bb397a869d",
  "tree": "01e8c10aa5b27fe5a8a739f1692969d27d9cf3ae",
  "parents": [
    "e6ea1ae6a36e1edff6f72be35eee4902e53b5d6b",
    "7f53271474ca601c3f3f2b1a1c2b9a6dfd821d42"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Mon Apr 06 08:27:50 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Apr 06 08:27:50 2026 +0200"
  },
  "message": "Rollup merge of #154561 - FranciscoTGouveia:typo-detection-after-visibility, r\u003dTaKO8Ki\n\nSuggest similar keyword when visibility is not followed by an item\n\nFixes rust-lang/rust#153353.\n\nI would appreciate feedback on the following:\n- I inlined [`find_similar_kw`](https://github.com/rust-lang/rust/blob/cd14b73b4a41542d921f59e362a5b5005fa4f2ef/compiler/rustc_parse/src/parser/diagnostics.rs#L218-L224) instead of changing its visibility to `pub(super)`. I am happy to switch if it is preferred;\n- I didn\u0027t add a comment to the new test. Although the rustc-dev-guide specifies that a [comment should be added](https://rustc-dev-guide.rust-lang.org/tests/adding.html#comment-explaining-what-the-test-is-about) to every new test, this is not common in `tests/ui/parser/misspelled_keywords/` and the test seems self-explanatory. Let me know if you would like me to add a comment;\n\nThank you in advance for your time and input!\n",
  "tree_diff": []
}