cuda-api-wrappers
Thin C++-flavored wrappers for the CUDA Runtime API
|
: Should we really expose the region parent class? We could, instead, have a get()
or region()
method which provides lvalue-ref access to it.
: Should this be called a unique_region
, a-la-unique_ptr
? Or perhaps unique_ptr
is a misnomer, and should have been called owned_ptr
(as opposed to shared_ptr
), and regardless, this should be called an owned_region
?
consider adding load_module methods to context_t
When switching to the C++17 standard, use string_view's instead of the const char* and ::std::string reference
::std::filesystem::path
's. In C++17, consider making the elements ::std::filesystem::path
's.
Check how these strings are interpreted. Do they need quotation marks? brackets? full paths?