-
Notifications
You must be signed in to change notification settings - Fork 71
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
async #13
async #13
Conversation
I spent some time trying to wrap |
@@ -16,6 +16,7 @@ license = "Apache-2.0" | |||
ctrlc = "3.1" | |||
http = "0.2" | |||
log = "0.4" | |||
macro_rules_attribute = "*" |
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.
@alsuren I'm hesitant to add this dependency. Perhaps instead we can implement this as a macro in goose_codegen
, and generally add other macros in this dependency to improve goose ergonomics? (The code currently in there can be removed).
I don't like that it's a 0.0.1 release, that I don't see any other modules using it on crates.io, and that we have to invoke it before every load test function.
It's a bit of a shitshow because of lifetimes, and the fact that async functions can't be used as function pointers (because the return value is not sized predictably in a dynamic context). This thread was really hepful to me: https://users.rust-lang.org/t/how-to-store-async-function-pointer/38343/4 All that's left to do is: * Fix the doctests * Actually try out the examples and see if they are still working/performant. * Go hunting for places where explicit threads are used which could be turned into tasks.
Closing in favor of #22 |
I've rebased #8 onto latest
master
so we can continue this effort.