[C++23] [Modules] Compile error: different definitions in different modules

[JinHai-CN]

Hi guys, Our project is using c++20 and applied modules feature. But when we compile it with c++23, we get the following error.

Is there a problem with the STL I'm wrapping or something else?

Clang: Ubuntu clang version 18.1.0 (++20240203081317+140ad18e1ea2-1exp120240203201335.24)

[llvmbot]

@llvm/issue-subscribers-clang-modules

Author: Jin Hai (JinHai-CN)

Hi guys, Our [project](https://github.com/infiniflow/infinity) is using c++20 and applied modules feature. But when we compile it with c++23, we get the following error.

Is there a problem with the STL I'm wrapping or something else?

Clang: Ubuntu clang version 18.1.0 (++20240203081317+140ad18e1ea2-1exp120240203201335.24)

[dwblaikie]

Can't seem to load the image - and generally a copy/paste of the text is more usable for everyone than a screenshot. If you could include the copy/pasted text, that'd be handy, thanks!

[ChuanqiXu9]

While I can't see the image either, I guess this is related to #79959 (You can read the document to get the rationale). For verifying, you can either compile a clang from source in trunk or wait for the next RC of clang18 in the next week.

[JinHai-CN]

Can't seem to load the image - and generally a copy/paste of the text is more usable for everyone than a screenshot. If you could include the copy/pasted text, that'd be handy, thanks!

No problem. At first, I plan to paste the text, which is not readable from my view. So I give the screen shot. OK, I will give the error text.

[JinHai-CN]

While I can't see the image either, I guess this is related to #79959 (You can read the document to get the rationale). For verifying, you can either compile a clang from source in trunk or wait for the next RC of clang18 in the next week.

Ok, I will wait for the next clang-18 RC.

[ChuanqiXu9]

Can't seem to load the image - and generally a copy/paste of the text is more usable for everyone than a screenshot. If you could include the copy/pasted text, that'd be handy, thanks!

No problem. At first, I plan to paste the text, which is not readable from my view. So I give the screen shot. OK, I will give the error text.

It is still images. I'll suggest to copy the text directly next time.

While I can't see the image either, I guess this is related to #79959 (You can read the document to get the rationale). For verifying, you can either compile a clang from source in trunk or wait for the next RC of clang18 in the next week.

Ok, I will wait for the next clang-18 RC.

I just saw the patch is included in the new clang-18 RC: https://github.com/llvm/llvm-project/commits/llvmorg-18.1.0-rc2/

[JinHai-CN]

Can't seem to load the image - and generally a copy/paste of the text is more usable for everyone than a screenshot. If you could include the copy/pasted text, that'd be handy, thanks!

No problem. At first, I plan to paste the text, which is not readable from my view. So I give the screen shot. OK, I will give the error text.

It is still images. I'll suggest to copy the text directly next time.

While I can't see the image either, I guess this is related to #79959 (You can read the document to get the rationale). For verifying, you can either compile a clang from source in trunk or wait for the next RC of clang18 in the next week.

Ok, I will wait for the next clang-18 RC.

I just saw the patch is included in the new clang-18 RC: https://github.com/llvm/llvm-project/commits/llvmorg-18.1.0-rc2/

Yes, it is fixed.