Sharadh Rajaraman
Sharadh Rajaraman
There's a bit of a problem here and I'd like some thoughts. I'm defining the macro `VULKAN_HPP_CPP_STD_MODULE` in `vulkan_hpp_macros.hpp` based on the platform and compiler characteristics. This means we need...
@M2-TE now that we've merged in #2303 maybe we can work towards resolving and closing this, also now that most recent compilers are happy to support named modules. I need...
I'm not sure that is a good resolution: [this blog post](https://vector-of-bool.github.io/2019/10/07/modules-3.html) says: > C++ Modules is almost entirely agnostic to the existence of the preprocessor. What you’ve just done in...
I think your initial claim is misconstrued—you've quoted the standard: > http://eel.is/c++draft/cpp#import-3: > If a [pp-import](http://eel.is/c++draft/cpp#nt:pp-import) is produced by source file inclusion (including by the rewrite produced when a #include...
Actually, I misconstrued that myself too. That line refers to a module 'group', which is the part between `export module vulkan_hpp;` and the end of the file, or `module :private;`....
I'm not entirely sure why the CI tasks are failing so badly... @asuessenbach, any thoughts?
Now that you mention it, I do see that build failure on MSVC, but I'm not sure it's relevant to this PR. In particular, https://github.com/KhronosGroup/Vulkan-Hpp/blob/d86b49ca041b9be51afb105668312925719845d0/tests/UniqueHandleDefaultArguments/UniqueHandleDefaultArguments.cpp#L29 needs to be: ```diff -...
Right, I've resolved it. If the macros in `vulkan_hpp_macros.hpp` depend on `vulkan.h` then it only makes sense to `#include` the latter in the former, which I've done.
Ready to merge.
@stripe2933 while the CI completes, if you could test this out that'd be great. Refer to https://github.com/KhronosGroup/Vulkan-Hpp/blob/41db2194537c8863927735e2500e326e65e5a0a8/tests/CppStdModule/CMakeLists.txt if you'd like to see how to set it up.