This includes the .ixx extension and the .cppm extension for different components of a named module.

Ideally you wouldn't use that extension at all because clang silently doesn't emit object files for it, requiring -x c++. But if you think that is important, at the very least it should only be done for actual modules. https://github.com/mathstuf/cxx-modules-sandbox/blob/master/link-use/use.mpp is particularly incorrect because currently main() isn't allowed to be defined inside of a module.

I'm getting the following error:

error: ‘import’ does not name a type; did you mean ‘short’?

What am I doing wrong?

Ubuntu 18.04
CMake 3.17.0
GCC 7.5.0

Some other use cases to add to this repository that I've mentioned elsewhere (Slack or Reddit):

• generated sources
• code that can confuse naïve scanners:

const char* foo = "
#include <vector>
import M;
";

• module names expanded from macros (import and export)
• module names expanded from macros on the command line (import and export)
• overlapping file basenames (foo.mpp and foo.cpp)

Something to make and upload Docker images from the docker branch should be done. I looked at Docker Hub's support, but it wants write access to all repositories which I cannot justify, so something else would need to be done (possibly also Cirrus CI (#1)?).

There's the Docker image with the tools all prebuilt. This should be used for testing.

Hello, and thanks for this repo,

It is very helpful as c++20 modules are a very attractive feature of the latest standard.
In an effort to configure the project, cmake throws the following configuration error (on Windows):

target_sources File set TYPE may only be "HEADERS"

So, I'd like to ask you if a need a specific cmake version for this to work (currently I am using version 3.23.1).

Thank you very much in advance!

Hi,
what is the difference between named/mymodule_part_impl and named/mymodule_part_internal ?

you mention MSVC specifics -internalPartition but i don't see the difference between the two files but you wrote that we need to build part_impl without -internalPartition and part_internal with it

Build2 supports modules. Build support for it would be nice to have for comparison.

Cc: @boris-kolpackov

This is bullet 3 of the p1703 proposal that was extended to cover named modules as well as header units.

This was the main test my implementation was failing, and now I'm happy I don't have to fix it 😄

It is suspected that this will cause errors due to different macro expansions and BMI incompatibility errors.

Currently, -fvisibility=hidden causes module initializer symbols to be hidden. There is no way to tell GCC to export these symbols as __attribute__ is not allowed near the export module line.

Primarily:

• .mpp extensions for module interface files (with an example not using this extension)
• match module names with file basenames (with an example using mismatching names)

See discussion in #3.

There are patches to GNU Make to support GCC's module mapper socket. Example code for using it would be nice to have.

@urnathan

It is still on Cirrus-CI.