Prevent ICE when formatting an empty-ish macro arm #5833
Merged
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 #5730
Previously rustfmt was attempting to slice a string with an invalid range (
start > end
), leading to the ICE.When formatting a macro transcriber snippet consisting of a lone semicolon, the snippet was being formatted into the empty string, leading the enclosing
fn main() {\n}
added byformat_code_block
to be formatted intofn main() {}
. However, rustfmt was assuming that the enclosing function string's length had been left unchanged. This was leading to an invalid range being constructed when attempting to trim off the enclosing function.The fix is to just clamp the range's start to be less than or equal to the range's end, since if
end < start
there's nothing to iterate over anyway.Hi rustfmt'ers! This is my first PR to the project. I'm still not too familiar with the codebase, so hopefully I'm doing this right. Any feedback is welcome.