Matthew Koscumb

I wouldn't be opposed to providing getters and setters, should that be the existing style. That said, if and unless there are validation operations performed on those methods, I'm hesitant...

Agreed that the default user case should be as simple as possible if they're not in the business of configuring the SDK. If we've got time I'm good with discussing...

> evt_task_t ? That still breaks from the POSIX standard requirement of reserving any types that end with underscore-t, I'm fine with evt_* as the prefix, especially if we use...

EDIT: I stand corrected, Windows does provide an optional POSIX implementation https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux. That said, windows.h (and subheaders in the SDK) defining _t types is allowed, as it itself is the...

How is using a std::chrono type inconvenient? Not only does it prevent mistakes from assumptions around the period of the data (does the uint64_t represent seconds? milliseconds? nanoseconds? 100ns (like...