Conversation
…obstacle_factory_test
…into william/bazel9 # Conflicts: # src/toolchains/cc/BUILD
…into william/bazel9
…into avah/bazel9_pyqt6_fixes
GrayHoang
requested review from
Andrewyx,
sauravbanna and
williamckha
as code owners
September 6, 2026 01:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
There is a set of macros defined in
sml_fsm.hthat are supposed to make using Boost::SML a bit easier for members. While it does simplify the context, it obfuscates a lot of what's going on under the hood, and makes debugging and logging more difficult.This PR removes all of those macros and replaces them with what they actually represent, in the case of State and Event macros.
It also defines a series of template classes to wrap action and guard functions into functor classes while preserving their context, to make logging and debugging easier (see #3489 for the potential applications of this).
This is a direct improvement over the macro I defined in #3489.
Testing Done
Compiles, thunderscope runs.
Resolved Issues
Length Justification and Key Files to Review
Most of the changes are just replacing the macro with an object initialization.
Please look at
software/util/sml_fsm/sml_fsm.h.Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.hfile) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO(or similar) statements should either be completed or associated with a github issue