arbiter
arbiter copied to clipboard
enhance(arbiter-engine): allow `Behavior`s to get their own `Coprocessor`
Idea
The Coprocessor
is ready to be tested and used. What better use case is there than giving all of your behaviors a way to have their own scratch pad that won't block the main tx stream? This is the way!