Open
Conversation
Member
|
Would you mind explaining what the root problem is and why it needs a ~18K line patch to fix it? |
Contributor
Author
yes, sorry the long detail but I am here to explain :)
I know this PR reads "too forward", but once CRAN starts testing compiled code with C++23, this issue will show up. The current Catch 1.9 that testthat uses works perfectly well with <= C++20 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CXX23 is strict about the lhs operand, which means the current Catch version (1.9.6) used with testthat will cause multiple compilation errors not because of the tested package but because of the vendored Catch header.
This PR shows the scripts I used to use Catch2 with testthat.
I implemented this after noticing that cpp4r does not pass all tests when enforcing CXX23 with the GNU compiler.