-
Would you like to wrap any pointer data members with the class template “[std::unique_ptr](https://en.wikipedia.org/wiki/Smart_pointer#unique_ptr "Description for the usage of smart pointers")”?
Up…
-
At present liboi uses standard pointers. Although this is fine, memory leaks could be easily introduced if new functions/routines are added in the future. Instead we should switch to std::shared_ptr…
-
After discussing my thought on #398 with Damon: we should have ScopedPtr and SharedPtr inherit from their underlying pointers (to allow code to be written using those types without ::Type suffixes) bu…
-
When we call cudaMemcpy with smart pointers, it incurs compile errors
``` cpp
tree.cpp(101): ERROR : no suitable conversion function from "std::shared_ptr" to "const void *" exists
```
Need to fin…
-
Refactor code to use smart pointers and to be const-correct. I've already ran into a lot of issues using raw pointers. Const-correct code is less error prone and looks cleaner.
vexyl updated
6 years ago
-
I think most of the `shared_ptr` we have should be `unique_ptr`
what do you think? @luca-heltai?
-
In this file onnxruntime_cxx_api.h
If I use version 1.12.x and below
char* LookupCustomMetadataMap(const char* key , OrtAllocator* allocator )const;
///< Wraps OrtApi :: ModelMetadataLookupCustomMe…
-
The parser component leaks so much memory that we decided at some point to put it into its own executable s.t. the memory leaks do not affect the search. Introducing smart pointers where possible is a…
-
-
Personally, I think the C++11 standard is old enough (8 years old!) that we can begin using it. And it comes with some great added features! Like the smart pointer types `std::unique_ptr`, `std::share…