Kevin Dewald

This can mess with thread-safety mechanisms on user implementations that expect callbacks to always come from a different thread.

Based on this example code: ``` #include #include #include #include using Callback = std::function; using CallbackProvider = std::function; Callback callback; void SetCallbackIfUnset(CallbackProvider provider) { // Take mutex protecting `callback` if...

https://stackoverflow.com/a/68389344

### Confirmed - [ ] Directed scan for specific services. ( See https://github.com/OpenBluetoothToolbox/SimpleBLE/issues/52#issuecomment-1100454264 ) - [ ] Add API documentation. - [x] Proper error handling for MacOS. - [ ]...

This is to prevent side effects from interacting with these objects from multiple threads.

Investigate potential redefinition of ByteArray

1

Would it make sense to treat it as a basic string of unsigned char? ``` using ByteArray = std::basic_string; ```

## Known Issues / To-Do's - [Linux] Fork safety is not guaranteed. - [MacOS] Only the main system adapter can be detected. - [MacOS] Implementation has incomplete error handling and...