hubcio commented on PR #2661: URL: https://github.com/apache/iggy/pull/2661#issuecomment-3840996566
Tests should now pass, i merged #2667 and rebased your PR. Regarding 3: event loop - the current design calls `RUNTIME.block_on()` for every operation, so every C++ call blocks until the async Rust code finishes. That works fine for simple use cases, but for anything high-throughput (continuous polling, concurrent sends), users would need threads on the C++ side to work around it. So, my rephrased question is: do you have any plans to expose async APIs (callbacks, futures, or letting users drive the runtime), or is blocking the intended final design? I'm fine with either, just keep in mind that at some point in future we want to add proper sans-io based Rust SDK. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
