ENH: Changed test macros to copy result - #1709
Draft
JDuffeyBQ wants to merge 1 commit into
Draft
Conversation
- Wrapped inside do while block for formatting - Now check that the argument to the macros is actually a Result Signed-off-by: Jared Duffey <jared.duffey@bluequartz.net>
Comment on lines
+48
to
+49
| { Result{x} } -> std::same_as<T>; | ||
| }; |
Contributor
There was a problem hiding this comment.
[clang-format] reported by reviewdog 🐶
Suggested change
| { Result{x} } -> std::same_as<T>; | |
| }; | |
| { | |
| Result{x} | |
| } -> std::same_as<T>; | |
| }; |
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.
Fixes #1704
SIMPLNX_RESULT_REQUIRE_VALIDandSIMPLNX_RESULT_REQUIRE_INVALIDnow assign the inputResult<T>to avoid macro duplication when the argument is an expression (may copy or move depending on input type).For tests, I think the following typical form should still be preferred since it allows for easy access to the
Resultin the debugger. This PR mainly serves as a guard against unintended behavior.