Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tools: update clang/gcc support tables #2

Merged
merged 1 commit into from
Apr 27, 2024

Conversation

mathstuf
Copy link
Contributor

GCC 14 will contain P1689 support. Clang 18 supports import std via libc++.


Of course, even MSVC's C++20 module support should probably be "Partial" given that there are likely many bugs yet to be discovered.

GCC 14 will contain P1689 support. Clang 18 supports `import std` via `libc++`.
@kelteseth kelteseth merged commit 051db27 into kelteseth:master Apr 27, 2024
@kelteseth
Copy link
Owner

Thank you 😊

@mathstuf mathstuf deleted the patch-1 branch April 27, 2024 13:35
@kelteseth
Copy link
Owner

@mathstuf Do you think we should add a tier level of support to modules? When looking at the comments of this PR, we can see that even using a none modules project as a dependency can make problems in a modules project. My proposal:

  1. LibraryX can be used in a modules project
  2. LibraryX itself is a modules project
  3. All of LibraryX dependencies are modules
  4. LibraryX uses C++23 import std;
  5. All of LibraryX dependencies are using C++23 import std;

@mathstuf
Copy link
Contributor Author

Tracking module-related issues might be useful? Something that works with compiler X and fails with Y might be worth tracking (with a link to an example project/standardese). There are definitely issues around mixing headers and modules today, but I believe there is work underway to address them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants