PR #104 was rejected because it was not the strategy to support both import std and #include at the same time.
I am wondering if a PR that did the following would be acceptable
#if !defined(IFC_DONT_INCLUDE_STANDARD_LIBRARY_HEADERS)
#include <vector>
#endif
No mention of import std anywhere.
This would allow users to define IFC_NO_STANDARD_LIBRARY_INCLUDE and use import std.
I am really concerned that waiting for all compilers, CMake and every other part of the ecosystem to be perfect is still a long way away.
Note the current work around I use is to create empty version of every standard library header like <vector>. Then I change my include path to include these rather than the real headers and then include IFC headers. This is obviously pretty ugly!
PR #104 was rejected because it was not the strategy to support both
import stdand#includeat the same time.I am wondering if a PR that did the following would be acceptable
No mention of
import stdanywhere.This would allow users to define
IFC_NO_STANDARD_LIBRARY_INCLUDEand useimport std.I am really concerned that waiting for all compilers, CMake and every other part of the ecosystem to be perfect is still a long way away.
Note the current work around I use is to create empty version of every standard library header like
<vector>. Then I change my include path to include these rather than the real headers and then include IFC headers. This is obviously pretty ugly!