)]}'
{
  "commit": "2d0504236c7236345ee17a0cb43a3bb9ce3acf7f",
  "tree": "2f8c0092c49a8e7333674a6e20bbc111b0ea445f",
  "parents": [
    "7dea652169d3f5333db8a286248c66ba94e1efe0"
  ],
  "author": {
    "name": "Than McIntosh",
    "email": "thanm@google.com",
    "time": "Thu Nov 14 11:47:58 2019 -0500"
  },
  "committer": {
    "name": "Ian Lance Taylor",
    "email": "iant@golang.org",
    "time": "Fri Nov 15 03:28:14 2019 +0000"
  },
  "message": "compiler: fix buglet in function inlining related to sink names\n\nWhen the compiler writes an inlinable function to the export data,\nparameter names are written out (in Export::write_name) using the\nGogo::message_name as opposed to a raw/encoded name. This means that\nsink parameters (those named \"_\") get created with the name \"_\"\ninstead of \"._\" (the name created by the lexer/parser). This confuses\nGogo::is_sink_name, which looks for the latter sequence and not just\n\"_\". This can cause issues later on if an inlinable function is\nimported and fed through the rest of the compiler (things that are\nsinks are no recognized as such). To fix these issues, change\nGogo::is_sink_name to return true for either variants (\"_\" or \"._\").\n\nFixes golang/go#35586.\n\nChange-Id: I5cddebca0d30932ac76ebd5ca8e765d849323b35\nReviewed-on: https://go-review.googlesource.com/c/gofrontend/+/207259\nReviewed-by: Ian Lance Taylor \u003ciant@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e742b6eb8e3f9af07fd6422d4f19651b2063af0b",
      "old_mode": 33188,
      "old_path": "go/gogo.h",
      "new_id": "8b791168894686f236baa228da737a60a4360073",
      "new_mode": 33188,
      "new_path": "go/gogo.h"
    }
  ]
}