sol2/docs/source/codecvt.rst

std::(w/u16/u32)string support
==============================
because this is surprisingly hard using standard C++
----------------------------------------------------

Individuals using Visual Studio 2015, or on Windows with the VC++ and MinGW compilers (possibly Clang++ on Windows as well) have ``<codecvt>`` headers, and thusly Sol will attempt to include it. Individuals on GC 4.9.x, Clang 3.5.x, Clang 3.6.x do not seem to have ``<codecvt>`` shipped with the standard library that comes with installation of these compilers. If you want ``std::wstring``, ``std::u16string``, ``std::u32string`` automatic handling then you need to make sure you have those headers and then define ``SOL_CODECVT_SUPPORT`` on unsupported compilers.

ThePhD did not want this to have to be a thing, but slow implementations and such force their hand. When GCC 7.x comes out, ThePhD will consider removing the effect of defining this macro and leaving <codecvt> support in at all times.
Turns out C++ sucks when all implementers don't do things equally as fast. WHO KNEW? 2016-08-13 01:08:59 +08:00			`std::(w/u16/u32)string support`
			`==============================`
			`because this is surprisingly hard using standard C++`
			`----------------------------------------------------`

improve docs heavily 2016-11-12 01:44:34 +08:00			Individuals using Visual Studio 2015, or on Windows with the VC++ and MinGW compilers (possibly Clang++ on Windows as well) have ``<codecvt>`` headers, and thusly Sol will attempt to include it. Individuals on GC 4.9.x, Clang 3.5.x, Clang 3.6.x do not seem to have ``<codecvt>`` shipped with the standard library that comes with installation of these compilers. If you want ``std::wstring``, ``std::u16string``, ``std::u32string`` automatic handling then you need to make sure you have those headers and then define ``SOL_CODECVT_SUPPORT`` on unsupported compilers.
Turns out C++ sucks when all implementers don't do things equally as fast. WHO KNEW? 2016-08-13 01:08:59 +08:00
[ci skip] be clear in docs about inheritance usage 2016-08-15 00:12:48 +08:00			`ThePhD did not want this to have to be a thing, but slow implementations and such force their hand. When GCC 7.x comes out, ThePhD will consider removing the effect of defining this macro and leaving <codecvt> support in at all times.`