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.
@Schmluk Found a somewhat workable solution for handling the full-stream precision that yaml-cpp uses under the hood for floating-point representations. Other notes:
gtest_discover_tests
back (I'm hoping I found the right arguments to avoid the weird linking issue that happens in catkin that made me remove it originally) so we can use ctestas<unsigned>
on a literal with a negative sign)gtest_discover_tests
isolates each test into a single executable already).Lmk what you think about the float formatting. We can also talk in-person about the what else I tried, I don't think there's an easy way to get around the edge-cases to my solution (i.e., string fields that are look like really long floats) without a much more substantial overhaul to support tracking which scalars are floats.