What the developer wrote
Authored by Suhas Daftuar
Allow moving an Epoch::Marker
What changed, and why it matters
This tiny change allows a small internal bookkeeping object (Epoch::Marker) to be moved in memory rather than copied. The commit message gives no security context. By itself this is a routine C++ cleanup; it does not obviously fix or introduce a vulnerability, though it slightly changes object lifetime behavior.
No immediate action needed. Treat as routine maintenance unless a follow-up commit or advisory ties this change to a concrete security issue.
Security signals we found
No security keywords in commit title or message
No referenced CVE, advisory, or security report
Change is a two-line C++11 move-semantics defaulting
No functional logic change visible in the diff
Evidence from the diff
The patch changes Epoch::Marker’s move constructor and move assignment from deleted to defaulted. This makes the type movable. The Marker is a nested class inside Epoch in src/util/epochguard.h, used as part of an RAII guard pattern. There is no direct evidence in the diff or references that this change is security-relevant; it appears to be a code-quality/ergonomics change to satisfy move semantics for containers or return values.
Changed components
src/util/epochguard.hEpoch::Marker classInspect captured patch +2 / −2
diff --git a/src/util/epochguard.h b/src/util/epochguard.h
index 145f4dc1..25ae3ac7 100644
--- a/src/util/epochguard.h
+++ b/src/util/epochguard.h
@@ -59,8 +59,8 @@ public:
public:
Marker() = default;
Marker(const Marker&) = default;
- Marker(Marker&&) = delete;
- Marker& operator=(Marker&&) = delete;
+ Marker(Marker&&) = default;
+ Marker& operator=(Marker&&) = default;
~Marker() = default;
};
Why this scored 11/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.