refactor!: avoid hard dep to tokio rt#4061
Conversation
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
|
We need to make blocking layer under a feature gate instead. This is a breaking change. |
|
@Xuanwo I have an alternative idea. I'm investigating |
Signed-off-by: tison <wander4096@gmail.com>
This reverts commit 64362a0.
Replacing tokio this way doesn't look good to me. I like the idea of using pollster, but I wish it to be a new layer like In this way, our users can decide which runtime to use by switching layers in the next version. |
This is the case. Switching to a feature flag solution. |
d8313ea to
7d885c5
Compare
659142e to
b9f161e
Compare
Signed-off-by: tison <wander4096@gmail.com>
b9f161e to
9e91d97
Compare
Signed-off-by: tison <wander4096@gmail.com>
Xuanwo
left a comment
There was a problem hiding this comment.
Mostly LGTM, the only thing here is to add a upgrade entry in UPGRADE.md since this is a breaking change.
Signed-off-by: tison <wander4096@gmail.com>
This closes #3948.
I'm trying to opt-out tokio deps as much as possible. But it surprises me that simply remove "rt" doesn't give compile error locally. Check CI workflow for more infos.