)]}'
{
  "commit": "fb2dea78b4a62307fde09c3700250393d8470f61",
  "tree": "968a79ab697bfa023cdc0a564597b4ba131d1a8d",
  "parents": [
    "7ff86095f361ea5ef5f1810d85bf9d325f68a95e"
  ],
  "author": {
    "name": "JOE1994",
    "email": "joseph942010@gmail.com",
    "time": "Sun May 31 13:46:14 2020 -0400"
  },
  "committer": {
    "name": "JOE1994",
    "email": "joseph942010@gmail.com",
    "time": "Sun May 31 13:46:14 2020 -0400"
  },
  "message": "Replace \u0027clone_from_slice\u0027 with \u0027copy_from_slice\u0027\nCurrently, \u0027shared_memory::safe_copy\u0027 uses \u0027clone_from_slice\u0027 to\nperform memory copy. \u0027clone_from_slice\u0027 iterates over each element of\nslice to invoke \u0027clone_from\u0027. According to docs of \u0027clone_from_slice\u0027, it can be\nmore performant to use \u0027copy_from_slice\u0027 instead when target slice\nimplements \u0027Copy\u0027(https://doc.rust-lang.org/std/primitive.slice.html#method.clone_from_slice).\nSince \u0027\u0026[u8]\u0027 implements \u0027Copy\u0027, I thought replacing \u0027clone_from_slice\u0027\nwith \u0027copy_from_slice\u0027 would be a helpful change regarding\nperformance.\n\nThank you for reviewing this PR :)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "76e710e68952ad80ee61974c07b0aacd0973bc0a",
      "old_mode": 33188,
      "old_path": "core/src/shared_memory.rs",
      "new_id": "cac849d723bfbdfb47c40bd7186938fc5193f8af",
      "new_mode": 33188,
      "new_path": "core/src/shared_memory.rs"
    }
  ]
}
