Is there an existing issue for this?
Suggestion
In the convert.hpp there are multiple DynamicCopy methods. The ones that allocate strings use "malloc/free" and the ones that work with arrays of data use "new/delete" to allocate out the memory.
This should be using "new/delete" for all of the methods to make it simpler in the C# code for which deleting function to call when the code is done with the data.
Possible Implementation
No response
Anything else?
No response
Is there an existing issue for this?
Suggestion
In the convert.hpp there are multiple DynamicCopy methods. The ones that allocate strings use "malloc/free" and the ones that work with arrays of data use "new/delete" to allocate out the memory.
This should be using "new/delete" for all of the methods to make it simpler in the C# code for which deleting function to call when the code is done with the data.
Possible Implementation
No response
Anything else?
No response