Issues with current approach to mixing of C and C++ with regard to Visual Studio 15 2017
hartwork opened this issue · comments
According to #47 (comment) Visual Studio 15 2017 has issues to link against non-C++ defaultMemoryManager from C++ code. Conditional use of extern "C" may help.
Is defaultmemoryManager supposed to be accessible by users of the library, or is it just for the tests?
The latter: just the tests
Closing until 69066af turns out to be not the right fix.