Swift C++ interop and Windows

Update: It is well may be that the export * directive is indeed not needed if a Clang module only uses simple C types. I've briefly experimented with C++, expecting problems with C++ classes. But no, classes seemingly worked. Problems arose when using C++ strings. No problems when using the export * directive.

I've put back the recommendation to include the export * directive in module map files on my website.