)]}'
{
  "commit": "828c19de9292ddbca0e2da6a161c0c38124c5053",
  "tree": "f2bd76363af665ecb767d8894110d91e9fdd61e1",
  "parents": [
    "cf2a543085aaa479197f354a25e36a0e03dbd654",
    "c5748994cab06d2e4d2b1b985bbbbc0eb396cb28"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Fri Jun 26 11:49:30 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Jun 26 11:49:30 2020 +0000"
  },
  "message": "Merge #205\n\n205: Add a heap feature to libtock-rs/core. r\u003dgendx a\u003dgendx\n\nThis pull request adds a `heap` feature to the core crate of libtock-rs. This allows to configure the core crate to only enable and initialize the `HEAP` variable, while leaving the choice of defining a custom allocator.\r\n\r\nIndeed, the `HEAP` is conveniently initialized in the entry point with the app\u0027s heap start/size.\r\n\r\nAn example use case is in OpenSK (see this pull request https://github.com/google/OpenSK/pull/123), where the custom allocator can print some debugging information about allocations \u0026 deallocation to the console - while the heap implementation is the same as the default of libtock-rs (i.e. `linked_list_allocator`).\r\n\r\n---\r\n\r\nAn alternative to this feature could be to somehow communicate the app\u0027s heap start/size to the `main` function, so that each app can initialize its own allocator when the `alloc` feature is off.\n\nCo-authored-by: Guillaume Endignoux \u003cguillaumee@google.com\u003e\n",
  "tree_diff": []
}