You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Devices have numeric IDs ; streams and events actually use pointers to allocated structures, which are made (somewhat) opaque via type aliasing. We should not call these IDs... using "handles" is probably more appropriate.
This is relevant to both the develop and driver-wrapper branches.
The text was updated successfully, but these errors were encountered:
* Now using "event handle", "stream handle" rather than "event id", "stream id" respectively.
* Implemented `detail_::identify()` variants for streams and events, and placed them together with the device identifier in `error.hpp`.
* Now using "event handle", "stream handle" rather than "event id", "stream id" respectively.
* Implemented `detail_::identify()` variants for streams and events, and placed them together with the device identifier in `error.hpp`.
* Now using "event handle", "stream handle" rather than "event id", "stream id" respectively.
* Implemented `detail_::identify()` variants for streams and events, and placed them together with the device identifier in `error.hpp`.
* Now using "event handle", "stream handle" rather than "event id", "stream id" respectively.
* Implemented `detail_::identify()` variants for streams and events, and placed them together with the device identifier in `error.hpp`.
Devices have numeric IDs ; streams and events actually use pointers to allocated structures, which are made (somewhat) opaque via type aliasing. We should not call these IDs... using "handles" is probably more appropriate.
This is relevant to both the develop and driver-wrapper branches.
The text was updated successfully, but these errors were encountered: