Address rustfmt differences for re-enabled rustfmt CI/CD check #1008
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.
Issue #, if available: n/a
Description of changes:
This PR is just the result of running rustfmt. With the changes made in #1006, the rustfmt check was re-enabled after some period of not being run in the workflow resulting in failures due to rustfmt diffs being detected.
In a few cases I added in
#[rustfmt::skip]
in order to maintain spacing in comments for multi-line byte slices that contained ion text equivalent comments. Otherwise, the changes are all rustfmt provided.Before PR
After PR
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.