Closed minexew closed 7 years ago
Thanks!
Neither gcc nor clang is producing this kind of warning, unfortunately I can't test it on Visual C++. Maybe it can be fixed by moving the explicit instantiations into the source rather than the header file, but that caused other problems for me.
This certainly shouldn't break anything (tested on Linux), and probably works for 32-bit builds as well.
There are still a bunch of warnings you might want to look into.