What the developer wrote
Authored by Abeeujah
Fix ArrayVec::try_push Doc comment
Correct the Doc comment to rightly reference `CapacityExceeded` instead
of `CAPSizeExceeded`.
What changed, and why it matters
This commit fixes a typo in a code comment (documentation). It changes the error name mentioned in a comment from 'CAPSizeExceeded' to 'CapacityExceeded' to match the actual code. There is no change to program logic, no bug fix, and no security relevance.
No action required; this is a documentation-only typo fix with no security or functional impact.
Security signals we found
No strong security signals were identified.
Evidence from the diff
Single-line documentation correction in internals/src/array_vec.rs for ArrayVec::try_push. The doc comment incorrectly referenced a non-existent ‘CAPSizeExceeded’ error; it now correctly references ‘CapacityExceeded’. The implementation was already using Error::CapacityExceeded, so this is purely a documentation consistency fix.
Changed components
internals/src/array_vec.rsInspect captured patch +1 / −1
diff --git a/internals/src/array_vec.rs b/internals/src/array_vec.rs
index e278afda..4be956ce 100644
--- a/internals/src/array_vec.rs
+++ b/internals/src/array_vec.rs
@@ -76,7 +76,7 @@ mod safety_boundary {
///
/// # Errors
///
- /// Returns `CAPSizeExceeded` if the `ArrayVec` is full.
+ /// Returns `CapacityExceeded` if the `ArrayVec` is full.
pub fn try_push(&mut self, element: T) -> Result<(), Error> {
if self.len >= CAP {
return Err(Error::CapacityExceeded(CAP));
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.