3 ms·
(author here) That's the intention! Protocol development, protocol testing. Think - leap seconds. While we don't support having different timer for each process
by majke 9y ago
(author here) That's the intention! Protocol development, protocol testing. Think - leap seconds. While we don't support having different timer for each process yet, this is easy to imagine.
Also - this is somewhat similar to golang race detector in spirit - looking for explicit synchronizations.
The general idea is that you should be able to run multiple processes within the thing, and that they should be able to just talk to each other freely.
There are a number of "protocol simulators" out there, but I always found them academic. I wanted to build a tool that will allow me run and test and do code coverage of my code, without having to wait forever for timeouts and timers to kick in to test rare branches.