hayodea d217354689 Add our first async thread sequence
Gave me some ideas about how things should be structured. Apparently
merely using region-data-locked threads doesn't eliminate the need
for synchronization/locking. It just means your synchronization is much
lighter, in the form of localized variables.

It seems we'll need to maintain boolean trackers for certain
operations that shouldn't be performed concomitantly, and deny
the caller access to those operations in order to preserve
data sanity.

I guess we still ended up using locking after all. Tbh, I'm not even
sure this will make things end up being lighter: we may have to bounce
requests off, or perhaps re-enqueue them into the queue?

So maybe instead of bouncing requests off, we could re-add them to the
rear of the queue when they conflict with an ongoing request.
2025-08-29 17:42:13 -04:00
2025-08-29 16:12:47 -04:00
2025-07-21 23:24:53 -04:00
2025-08-23 19:38:52 -04:00
2025-08-02 01:26:06 +00:00
2025-08-29 16:13:03 -04:00

The Salmanoff Project:

Salmanoff project

This project, Salmanoff (pronounced: Sal-man-off), is an ROS rewrite of the Harikoff project. The name is more reflective of the people whose ideas sparked the solutions in my mind. These people are:

  • Gregory SALmieri.
  • David HarriMAN.
  • Leonard PeikOFF.

Would you like to know what this project is and does? Well, it's a secret! But you can find out by reading the code. Or you could just ask me. Or you could wait until I release it. But that's no fun.

Languages
C++ 89.4%
CMake 6.1%
C 2.3%
Shell 1.3%
GDB 0.6%
Other 0.3%