CLR Object Stringify #1216
Merged
CLR Object Stringify #1216
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #1216 +/- ##
=========================================
- Coverage 82.24% 82.15% -0.1%
=========================================
Files 122 122
Lines 4726 4673 -53
=========================================
- Hits 3887 3839 -48
+ Misses 839 834 -5 |
horenmar
force-pushed
the
dev-clr-stringify
branch
from
717ca48
to
10514be
Compare
|
Thanks for the PR, I cleaned it up a bit before merging. |
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.
Changes to allow stringification of CLR objects. This enables REQUIRES(a == b) and such print proper strings in reports when used with CLR objects.
I have been using Catch2 in C++/CLI and this helps make it nicer.