You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 29, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: doxygen/style_suggestions.dox
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -245,7 +245,7 @@ Initially it was thought that state resuming could be done simply be re-publishi
245
245
246
246
Instead we opted of giving detectors this _know-all_ single chance to restore their state & re-publish any resumed state `TopicStates` as necessary.
247
247
248
-
TODO(cscotti): Example. A resuming version of @ref counterwithreset.cpp seems appropriate.
248
+
For a full example see [Resuming Counter](@ref resuminggraph.cpp) (@copybrief resuminggraph.cpp)
249
249
250
250
\section explicit-calls-to-evaluate Explicit calls to Evaluate()?
251
251
@@ -267,7 +267,7 @@ Instead the suggested pattern going forward is to always rely on `ResumeFromSnap
267
267
268
268
In the past we have used a specific `TopicState` (say `DetectorGraphInitialized`) that detectors can subscribe to to be notified when the system boots and publish any new state they may need to. That solution is redundant and not as canonical as the solution described above so it's not recommended anymore.
269
269
270
-
TODO(cscotti): Example. A resuming version of @ref counterwithreset.cpp seems appropriate.
270
+
For a full example see [Resuming Counter](@ref resuminggraph.cpp) (@copybrief resuminggraph.cpp)
0 commit comments