Format possiblyrandom cfg attributes
What the developer wrote
Authored by Joost Jager
Format possiblyrandom cfg attributes
Run rustfmt on the possiblyrandom crate so its cfg attributes match
the current formatting rules.
What changed, and why it matters
This commit is purely a code-formatting cleanup. It runs rustfmt on a small Rust source file so that multi-line conditional compilation (cfg) attributes are collapsed onto single lines. No logic, behavior, or security properties of the code change.
No security action needed. This is a cosmetic/style-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff only rewrites two #[cfg(any(…))] attributes in possiblyrandom/src/lib.rs from multi-line to single-line formatting. The cfg conditions, the extern crate declaration, and the getrandom::getrandom(dest) call remain identical. There are no functional changes.
Changed components
possiblyrandom/src/lib.rsInspect captured patch +2 / −8
diff --git a/possiblyrandom/src/lib.rs b/possiblyrandom/src/lib.rs
index 6ddbc6d..f27788d 100644
--- a/possiblyrandom/src/lib.rs
+++ b/possiblyrandom/src/lib.rs
@@ -20,19 +20,13 @@
#![no_std]
-#[cfg(any(
- feature = "getrandom",
- not(any(target_os = "unknown", target_os = "none"))
-))]
+#[cfg(any(feature = "getrandom", not(any(target_os = "unknown", target_os = "none"))))]
extern crate getrandom;
/// Possibly fills `dest` with random data. May fill it with zeros.
#[inline]
pub fn getpossiblyrandom(dest: &mut [u8]) {
dest.fill(0);
- #[cfg(any(
- feature = "getrandom",
- not(any(target_os = "unknown", target_os = "none"))
- ))]
+ #[cfg(any(feature = "getrandom", not(any(target_os = "unknown", target_os = "none"))))]
let _ = getrandom::getrandom(dest);
}
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.