What the developer wrote
Authored by Jad
AGENTS.md: prefer hex! literals
Documented the test-style preference in AGENTS.md to prefer hex!
literals for Rust unit-test byte arrays/constants.
What changed, and why it matters
This commit only updates an internal coding-style guide (AGENTS.md) for developers. It adds a recommendation to use a particular Rust macro (`hex!`) when writing unit tests. There is no code change, no bug fix, and no security relevance.
No action required; this is a non-functional documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one line to AGENTS.md instructing contributors to prefer hex! literals for byte arrays/constants in Rust unit tests. This is purely a documentation/style guideline; no firmware, test, or build code is modified.
Changed components
AGENTS.md (project documentation)Inspect captured patch +1 / −0
diff --git a/AGENTS.md b/AGENTS.md
index dfb1ca6..2b52289 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -53,6 +53,7 @@ security-sensitive areas.
- in Rust unit tests, prefer .unwrap() over .expect().
- In Rust unit tests, if testing a function foo, name the test `test_foo` (or `test_foo_xyz` if it needs qualifiers).
- in Rust unit tests, prefer .as_slice() instead of `&*` for wrapped/zeroized Vec<u8>.
+- in Rust unit tests, prefer `hex!` literals for byte arrays/constants.
## Review Guidelines
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.