)]}'
{
  "commit": "35d4cf0b9ac4e224bd9c6443db0489c5cb1e908c",
  "tree": "f7088549fd02356ca073a945c4179f8dc19233c3",
  "parents": [
    "511b040b970d35edeee1af25e7d6e03f993cf97d",
    "0189281105a815d5443ce1a0afd0a19ef74817ea"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Mon Dec 07 15:30:31 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Dec 07 15:30:31 2020 +0000"
  },
  "message": "Merge #261\n\n261: Begin overhauling libtock_platform\u0027s syscalls trait for Tock 2.0. r\u003dhudson-ayers a\u003djrvanwhy\n\nI made the following changes to the design of `Syscalls`:\r\n\r\n1. The trait is now designed for the (work-in-progress) Tock 2.0 syscalls rather\r\n   than the Tock 1.0 syscalls.\r\n2. The higher-level API that I previously intended to implement in the Platform\r\n   type is now expressed in the form of provided functions in Syscalls.\r\n\r\nSo far, I have only implemented `yield`. I\u0027m sending this for review now because it is already getting large, and I\u0027d prefer to split it up into several PRs rather than send a single huge PR.\r\n\r\nThere is still significant design work to be done in terms of error handling for `subscribe`, `command`, both `allow`s, and `memop`.\r\n\r\nEDIT: To everyone reviewing this, here is a [direct link to syscalls.rs](https://github.com/jrvanwhy/libtock-rs/blob/syscalls-2.0/core/platform/src/syscalls.rs), in case you want to read it *without* seeing the diff from the previous version.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}