)]}'
{
  "commit": "a8af2c3b643a892c0e4cc8f59efd16209f224228",
  "tree": "18864a2278cc91263fe3ff97bb6779bd475cf7f1",
  "parents": [
    "c3c80f29aca4b8a46e217125bc3753f5229046ac",
    "9785f9ae14eb9aa5b927cdc7236a94d91aa766ed"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Mon Jan 06 18:09:12 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jan 06 18:09:12 2020 +0000"
  },
  "message": "Merge #127\n\n127: Remove intrinsics r\u003dtorfmaster a\u003dtorfmaster\n\n# Summary\r\n\r\nThe error message when not enabling the `#![feature(core_intrinsics)]` feature reads\r\n\r\n\u003e use of unstable library feature \u0027core_intrinsics\u0027: intrinsics are unlikely to ever be stabilized, instead they should be used through stabilized interfaces in the rest of the standard library\r\n\r\nI think we should - unlike other nightly features which will hopefully be stabilized - not use this unless absolutely necessary. I removed the feature in a straightforward way, however. @jrvanwhy is the expert in that matter.\n\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}