)]}'
{
  "commit": "d399b9dfad740990e21bfa4d9dfa79729cff644b",
  "tree": "dd7980a9d307192fccf9a895b3eee6a32c3e535b",
  "parents": [
    "4a584df75de604a8b85a5ace13e5986c9bb8b14f",
    "9e00ef62c1608741e309eb10d4d934df8d2aa476"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Wed Aug 19 22:01:51 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Aug 19 22:01:51 2020 +0000"
  },
  "message": "Merge #231\n\n231: Remove `Allowed::replace` and `Allowed::take`. r\u003djrvanwhy a\u003djrvanwhy\n\nWhen I originally implemented `Allowed`, I made it work with non-`Copy` types. `Allowed::get` cannot with with non-`Copy` types, so I added `Allowed::replace` to allow client code to read a non-`Copy` type out of an `Allowed` buffer. However, during the PR review we changed `Allowed` to only contain `Copy` types. Because of this change, I don\u0027t anticipate `Allowed::replace` (and `Allowed::take` which is built on top of `Allowed::replace`) seeing much use. This PR removes `Allowed::replace` and `Allowed::take` to reduce the amount of `unsafe` in `libtock_platform`.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}