)]}'
{
  "commit": "d60e36596c6823abebabe7636af6ca981273792d",
  "tree": "fdfad690a9031c806cedb9540e2d96ce8416244c",
  "parents": [
    "4d27d242cb64b6b0a264bc5fb174b2e10f4fca20",
    "76f96bb4fe0b9278a48ba8c50872fd69ecfb4b9c"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Thu Mar 19 10:21:29 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Mar 19 10:21:29 2020 +0000"
  },
  "message": "Merge #164\n\n164: Split libtock into core and high level library r\u003dWoyten a\u003dtorfmaster\n\n# Summary\r\n\r\nIn order to address https://github.com/tock/libtock-rs/issues/160 we decided to do a first draft of splitting the library into parts. \r\n\r\nThe idea is that there are two layers:\r\n * libtock-core\r\n * libtock-rs\r\n\r\n(names tbd). Libtock-core contains the panic handler, the entry point, the allocator and the syscall interfaces. libtock-rs uses libtock-core and the interface stays as usual.\r\n\r\n# Possible Extensions\r\n\r\nWe deleted the \"blink\" code from the panic handler. This saves more than 1kbytes in the text segment. If this feature is still wanted we could implement the following:\r\n\r\n * provide a feature in libtock-core to opt-out  the panic handler in libtock-core\r\n * provide a feature for libtock-rs to opt-out the panic handler in libtock-core and using a blinking panic handler. \r\n\r\nIn the long run the (default) panic handler could exit the app and send debug information to the kernel which could print it for example. This could be implemented once the kernel functionality is in place.\r\n\r\n# Open questions\r\n\r\nThe current implementation of the panic handler more or less silently fails if there is a panic. Panics can be identified by enabling the \"trace_syscall\" option in the kernel. How should this be tackled?\r\nShould there be a default panic handling or should it be customizable and if yes how should it be customized?\n\nCo-authored-by: Woyten \u003cwoyten.tielesch@online.de\u003e\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}