| Issue |
172800
|
| Summary |
#include_next has unintuitive behavior with clang modules
|
| Labels |
clang
|
| Assignees |
|
| Reporter |
ian-twilightcoder
|
`#include_next` of a different header behaves differently with clang modules off and on. e.g. `<__mbstate_t.h>` in libc++ tries to `include_next <wchar.h>` to skip its own copy of that header. When modules are off, that successfully gets `<wchar.h>` from the C stdlib, but when modules are on it gets the one from libc++.
[include_next_reproducer.zip](https://github.com/user-attachments/files/24228641/include_next_reproducer.zip)
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
