You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested what you're thinking about adding an #[async_test] proc-macro to the futures-test crate.
There were previous discussions about it at #1169 (comment) and there are also some implementations existing already.
I have a kind of ugly (sry but I'm not good at proc-macros) but working implementation at futures-await-test-preview which uses futures_executor::LocalPool::new().run_until(), I'm not sure if this is better or worse then using block_on, for my use-cases it seems to work perfectly.
Currently I use my implementation to write tests for a Rust wrapper around an asynchronous C++ library, which uses only futures-0.3, not tokio. I find it really useful, perhaps others would too even if it uses futures-executor only at first. Later it could be somehow extended to support other executors as well..
Would you be interested in adding something like this to futures-test?
The text was updated successfully, but these errors were encountered:
Hi!
I'm interested what you're thinking about adding an
#[async_test]
proc-macro to thefutures-test
crate.There were previous discussions about it at #1169 (comment) and there are also some implementations existing already.
futures_executor::LocalPool::new().run_until()
, I'm not sure if this is better or worse then usingblock_on
, for my use-cases it seems to work perfectly.Examples for intended use-case:
Currently I use my implementation to write tests for a Rust wrapper around an asynchronous C++ library, which uses only
futures-0.3
, nottokio
. I find it really useful, perhaps others would too even if it usesfutures-executor
only at first. Later it could be somehow extended to support other executors as well..Would you be interested in adding something like this to
futures-test
?The text was updated successfully, but these errors were encountered: