Beginning of `stack-next` refactor
-Refactoring the protocol stack into something similar to a runtime. -Handles merging handler builders which is placing the ground work for plugins in. - Increased metadata generation during compilation enables less ser/de during execution. - Goal is to have an O(1) time from incoming operation to calling handlers. - Decreased penalty for using the statically typed API from within your code, now avoids some allocation. # Changes - Added `GiteratedRuntime` which is to replace the current unified stack - Added `RuntimeBuilder` which does what the current `OperationHandlers` struct does, but much better. - Added `RuntimeMetadata` to store type metadata for new `Any` based internals - Refactored serde_json out of the internal operation handling
parent: tbd commit: 708dea4
| 1 | use crate:: |
| 2 | OperationError, |
| 3 | , |
| 4 | GiteratedOperation, |
| 5 | ; |
| 6 | |
| 7 | use Debug; |
| 8 | |
| 9 | |
| 10 | |
| 11 | async |
| 12 | &self, |
| 13 | object: O, |
| 14 | operation: &str, |
| 15 | payload: D, |
| 16 | operation_state: &S, |
| 17 | |
| 18 | |
| 19 | O: GiteratedObject + Debug + 'static, |
| 20 | D: + Debug; |
| 21 | |
| 22 | async fn ( |
| 23 | &self, |
| 24 | object_str: &str, |
| 25 | operation_state: &S, |
| 26 | ) -> ; |
| 27 | } |
| 28 |