)]}'
{
  "commit": "6271253867a783ed6f2fe7d66c0ae62614515b1b",
  "tree": "e9852a213a5c690e38095e230d202f883e28c77f",
  "parents": [
    "12dc3d50514a4973cd9a198e7c6fd2686fba3b8c",
    "dc326a4071cf8ffd6ff118102a7447ff16b48826"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Wed Feb 26 22:33:17 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Wed Feb 26 22:33:17 2020 +0000"
  },
  "message": "Merge #125\n\n125: Create stream to stream events from ble scanning functionality merge after #122 r\u003dWoyten a\u003dtorfmaster\n\n# Summary\r\nIn this PR I migrate the ble scanning funtionality from callbacks to `futures::stream::Streams`. \r\nOnly merge after #122 \r\n\r\n# Questions/Help needed\r\n\r\n * I decided to make the `BleScanningDriverScanning::stream_values` method to consume `\u0026self` instead of `\u0026mut self`. While I think this is correct it may lead to unexpected behavior when two parallel Tasks consume this stream, i.e. the events are split between the consumers\r\n * I only implemented infinite streams as the stream of ble events will be either be stopped at runtime (to a point of time predictable at compile time) or continue to produce values forever.\r\n * I removed the possibilty of registering callbacks to the ble driver directly as for me it seemed to be only feasible for trivial business logic.\n\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}