Rustfmt tests that touch persistence#3882
Merged
TheBlueMatt merged 7 commits intolightningdevkit:mainfrom Jun 27, 2025
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Rustfmt preparatory PR for #3778.
My view on the changes is again that refactors, however trivial, are risky. Especially with large quantities of similar edits. In this PR I didn't do any touch ups for that reason.
Let me know what pressing, non-subjective formatting problems are really unacceptable. I can add a commit for those where I either change the formatting, or simpliy rustfmt::skip the section.