support using libcxx 17 #128
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Member
Author
|
Ready for review @conda-forge/clang-compiler-activation :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that conda-forge/libcxx-feedstock#131 has finally been merged, support its use with the cxx compilers. We cannot yet go back to the pre-17 days of just requiring
versionfor libcxx directly (c.f. db8e474) until we also have libcxx 18, which might still take a little while.Also, holding off on the release of 18 allows us to judge the impact of libcxx 17 on the broader ecosystem a bit better (and adapt to deprecations etc. as necessary), rather than jumping by 2 major versions in one go.