#clangd is has issues when module import is in a header file, and not the cpp file. This is not a problem for clang, its all in the same translation unit. AFAICT this is legal and fine C++20 module code, clangd shouldn't have this issue.

https://github.com/llvm/llvm-project/issues/181770

#cpp #cplusplus #cppmodules #llvm #programming

Did anybody successfully use C++ import std; on a mac with G++-15 and cmake 4.2.3 ?
I got as far as a linker error missing std module init and am too much of a cmake newbie to figure out anything working.

#cpp #cppmodules #cppimportstd #cmake

RE: https://fosstodon.org/@glloyd/115966242032349737

And now I fixed it, just needs to be merged.
https://github.com/llvm/llvm-project/pull/178471

#cpp #cplusplus #cppmodules #llvm #programming

Found bug in clang-tidy with C++20 modules. A single check can conflict with itself.

https://github.com/llvm/llvm-project/issues/178102

#cpp #cplusplus #cppmodules #llvm #programming

[EDIT: this is wrong, read thread]

Interesting #clangtidy issue.
When using #cppmodules its possible to have a fixit applies multiple times causing incorrect code.

I believe what is happening is the cppm is the source text, but its analysed in other translation unit by the module import which uses its pcm. In parallel they both read and apply their fixit and you get situations like NULL becoming nullptrptr.

I'll try and make a minimal example at some point.

#cpp #cplusplus

Any diagnostic to find cyclic dependencies?

set(CMAKE_CXX_SCAN_FOR_MODULES ON)
add_library(A STATIC)
target_sources(A PUBLIC
FILE_SET CXX_MODULES FILES mod.cppm # export module x;
)
target_link_libraries(A PRIVATE B)
add_library(B STATIC use.cpp) # import x;
target_link_libraries(B PRIVATE A)

All you get ATM is failure at compile time `fatal error: module 'x' not found`

But it would be nice to know that the real issue is that A and B make a cycle

#cplusplus #cppmodules #programming

What is the reasonable way to test internal parts of a module?

For a complex module I want unit tests for parts that I do not want to export. Do I make an internals module that can be tested. Then have the actual module which only re-export what I intend to be the library's interface?

#cpp #cplusplus #programming #cpp20 #cppmodules

Working with #cpp20 #cppmodules with #ninjabuild and #cmake

How can I run just the scan/dynamic based bits so that I can run clang-tidy without a full build?

ATM I have this hack
```
# cmake config
cmake --preset thing

# select what I need made
ninja -C build -t inputs | grep -E '\.cppm\.o$|\.o\.modmap$' | xargs -r ninja -C build

# then I can run clang-tidy
```

There must be a better way

#cpp #cplusplus #programming

C++ modules support status across FLOSS libraries.

https://arewemodulesyet.org/

#cc
#cplusplus
#cplusplusprogramming
#modules
#ccmodules
#cppmodules