)]}'
{
  "commit": "84c4bf25b784f26b9cac86faad9247a61ba6244b",
  "tree": "5777e31c5c768f94426fcb4a1c47aa09918da96f",
  "parents": [
    "c436ffe44ded235afbeb71cff49d6e9cf4ca25fa",
    "480616c7c872a1bea7031dac0ae57da8ca40d106"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Wed Mar 31 14:51:27 2021 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Mar 31 14:51:27 2021 +0000"
  },
  "message": "Merge #281\n\n281: Run Miri with more flag combinations, and add a Miri Tips doc. r\u003dalistair23 a\u003djrvanwhy\n\n[Rendered doc](https://github.com/jrvanwhy/libtock-rs/blob/miri-flags/doc/MiriTips.md)\r\n\r\nThis runs code under Miri with the `-Zmiri-symbolic-alignment-check` flag, as well as both with and without `-Zmiri-track-raw-pointers`. This identifies a lot of \"gray area\" behavior -- that may or may not become specified as undefined behavior in the future -- as undefined behavior.\r\n\r\nI also added a tip on how to write tests that identify undefined behavior that Miri doesn\u0027t catch by default, such as having uninitialized values in local variables. The documentation tip will be used in the `libtock_unittest` crate as well as per-crate unit tests.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}