And that covers the basics of #COROS and already, in my opinion, provides a better platform than most #RTOS implementations for small to mid-sized systems.

Then there's the advanced stuff. Note that events can pass *any* data type. And that an #EventQueue is a first-class data type. This means you can pass event queues around, π-calculus style, making it possible to provide subscribe/publish-style component connections, proxies, and other such systems with relative ease.

🧵 (5/n)

The second piece of the puzzle in the #COROS design is a segmented #EventQueue that applies a disciplined wrapper around the usual "one massive for loop testing and calling" that is the hallmark of #RealTime designs that don't use pre-emptive kernels. Event queues are chained and grouped in ways that allow any downstream queue to service events from any upstream queue, but not vice versa. Event handlers can be callback functions or #coroutines, depending on needs and complexity.

🧵 (3/n)