sml

Looks like SML is using user-defined literals [0, 1] to effectively pre-process the string literal into state/event objects. Looks like the string itself is turned into a template parameter in the process and I believe those shouldn't show up in the compiled code (maybe unless there's some mangling-related thing going on?) [0]: https://en.cppreference.com/w/cpp/language/user_literal.html [1]: https://github.com/boost-ext/sml/blob/f232328b49adf708737bef...

how is it better than https://github.com/boost-ext/sml ? there are about 1 million c++ state machines, and sml happens to be the best, or one of them. how does yours differentiate?

I recently was troubleshooting a crash that backtraced through the boost::sml library [0]. The crash didn't actually have anything to do with the library, but it was used as the core event loop. The backtrace -- as in, just the output from running `bt` in GDB -- was over a thousand wrapped lines long. There were ~5 stack frames that took up over a hundred lines of console each to print just the function name. That product's debug builds recently hit the 2GB line, which is enough that old versions of binutils complain. I don't know what the solution is. There's some really neat stuff you can do with template metaprogramming, and in stripped release builds it compiles down extremely tiny. Plus the code is very clean to read. But it does feel like there isn't any kind of central vision for the C++ debugging experience, and bad interactions b

At our company, we rely a lot on https://github.com/boost-ext/sml

A small experiment with https://www.arduino.cc and Modern C++ (C++14 for dev, C++20 for testing). > Goal * Verify whether development/simulation can be done fully online and with Modern C++. > Tools * Design: Plant UML - https://bit.ly/2GRos5N * Development: Compiler Explorer - https://godbolt.org/z/MfMdj9 * Implementation/State Machine: SML - https://github.com/boost-ext/sml * Unit Testing: UT - https://github.com/boost-ext/ut * Simulation: Tinker Cad - https://www.tinkercad.com/things/8rDYx57Ns7Q > Key takeaways * Compiler Explorer made it really easy to develop/test with different compilers * State Machines are great abstractions for hardware/bare metal * SML produced a fully optimized code for the AVR compiler * Tinker Cad made it really easy to simulate the results