What changed, and why it matters
This commit only reformats two lines of Rust source code. It does not change what the code does, only how it is visually laid out. There is no security relevance.
No action needed; this is a formatting-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff in rust/rust_c/src/common/qrcode/mod.rs is purely cosmetic: it collapses multi-line return statements onto single lines and removes unnecessary braces around a wildcard match arm. The logic, control flow, and error handling remain identical before and after the change.
Changed components
rust/rust_c/src/common/qrcode/mod.rsInspect captured patch +2 / −6
diff --git a/rust/rust_c/src/common/qrcode/mod.rs b/rust/rust_c/src/common/qrcode/mod.rs
index 3be170c..c519333 100644
--- a/rust/rust_c/src/common/qrcode/mod.rs
+++ b/rust/rust_c/src/common/qrcode/mod.rs
@@ -35,8 +35,7 @@ pub unsafe extern "C" fn parse_qrcode_text(qr: PtrString) -> Ptr<URParseResult>
if value.to_lowercase().starts_with("signmessage") {
if let Some((headers, message)) = value.split_once(':') {
if message.is_empty() {
- return URParseResult::from(RustCError::InvalidMessage)
- .c_ptr();
+ return URParseResult::from(RustCError::InvalidMessage).c_ptr();
}
let mut pieces = headers.split_ascii_whitespace();
let _ = pieces.next(); //drop "signmessage"
@@ -57,10 +56,7 @@ pub unsafe extern "C" fn parse_qrcode_text(qr: PtrString) -> Ptr<URParseResult>
)
.c_ptr();
}
- _ => {
- return URParseResult::from(RustCError::InvalidMessage)
- .c_ptr()
- }
+ _ => return URParseResult::from(RustCError::InvalidMessage).c_ptr(),
}
}
}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.