)]}'
{
  "commit": "773433dcd348767afa9493cfed0f299f21a6624d",
  "tree": "e514742a677befe3662366087a0c71464bdd0bc4",
  "parents": [
    "039d022ad6ec62e3a8fa550e860d9ea9af83d3ff",
    "7ca6f1b27a4679470b6e4f92f32da246afb49e1b"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Wed Aug 05 14:05:56 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Aug 05 14:05:56 2020 +0000"
  },
  "message": "Merge #221\n\n221: Add the `Syscalls` trait to `libtock_platform`. r\u003dhudson-ayers a\u003djrvanwhy\n\n`Syscalls` is a trait representing Tock\u0027s system call API. It will be implemented by both `libtock_runtime` (included by TBF binaries) and `libtock_fake` (included by unit tests). It will allow us to replace the real Tock kernel with a fake Tock kernel for testing purposes.\r\n\r\n`Syscalls` is designed to introduce no overhead over the system call assembly logic. For `allow`, `command`, and `subscribe`, it is based on Tock\u0027s `Driver` trait. A higher-level interface over Tock\u0027s system calls, for use by `libtock_core` and client code, will be introduced in a later PR.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}