Fixed panic!/assert! used with improper format strings #2033
+27
−36
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
marvin-bitterlich
approved these changes
Apr 6, 2021
Contributor
marvin-bitterlich
left a comment
marvin-bitterlich
left a comment
There was a problem hiding this comment.
looks sensible to me and clears up some of our warnings
sylvestre
reviewed
Apr 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
macros.rsused aStringwhere in the future a string literal will be expected.inputdecoder.rs's tests matched on aResultand assertedfalseon error.iirc the second argument also needs to be a string, but I've just turned the whole thing into an unwrap.