)]}'
{
  "commit": "e0237147ba6b53bff18585a6037faab4898b578b",
  "tree": "46b20a70ee739cd98952892fe79ed565e1cb9dc0",
  "parents": [
    "7913458c55eeb6ab181b470e669bd62325d3cab4",
    "6b119692b3986ee2a91ddab626393f064250b099"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Mon Nov 02 22:24:54 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Nov 02 22:24:54 2020 +0000"
  },
  "message": "Merge #247\n\n247: Document several factors constraining `libtock_core`\u0027s design. r\u003dhudson-ayers a\u003djrvanwhy\n\nThis Design Considerations document outlines a number of considerations that affect the design of `libtock_core` which do not impact most Rust projects. It is intended to help onboard new contributors and to remind long-term contributors of constraints that other `libtock_core` clients have.\r\n\r\n[Rendered document](https://github.com/jrvanwhy/libtock-rs/blob/design-doc/doc/DesignConsiderations.md)\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}