-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
abci: ADR-008 Merge abci-rs
into tendermint-rs
#510
Conversation
abci-rs
into tendermint-rs
abci-rs
into tendermint-rs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good and helps contextualize the upcoming merge. Small wording suggestions inline.
Co-authored-by: Alexander Simmerl <[email protected]>
Co-authored-by: Alexander Simmerl <[email protected]>
Co-authored-by: Alexander Simmerl <[email protected]>
Co-authored-by: Alexander Simmerl <[email protected]>
|
||
### Negative/Neutral | ||
|
||
- Developer is forced to use `async` Rust. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like what is described in (1) here and seems to be a possible convergence point amidst all the discussion to work towards, and something that is done in other rust crates, where the core is implemented synchronously and an async wrapper is provided. The extra maintenance cost for the wrapper seems minimal compared to the user/flexibility benefit, especially if the synchronous core is simple enough.
Would it make sense for abci2 to be used as such a core and adapt abci-rs to be an async wrapper around it, and expose both ?
Rendered