-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
enhancement(operations): abstracts runtime into runtime.rs #1098
enhancement(operations): abstracts runtime into runtime.rs #1098
Conversation
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 great! Thanks, left some comments :)
Roger, I'll address these this weekend! |
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
@Michael-J-Ward Hey! thank you for this! I ended up needing this for some tests I was running so I went ahead and just applied my changes, thank you a ton for doing all the heavy work! |
Thanks @Michael-J-Ward ! |
Hey @LucioFranco and @binarylogic , thanks for the true "Good first issue!" It was a great way for me to get my feet wet with Rust development. |
@Michael-J-Ward great! I hope to get more of these types of issues out! I hopefully will get to posting them to TWIR too. |
#1085
The
tokio
runtime is still leaking out viaShutdown
andTaskExecutor
types. I haven't taken time to investigate if those need to be wrapped or abstracted away in some other way.Additionally,
test_utils
andmain.rs
used thetokio::Builder
api to control the runtime's threadcount. Instead of creating a newBuilder
, I just provided alternate constructor methods onRuntime
.And obviously, I haven't implemented a free standing
spawn
function yet.But other than that, it compiles and tests are passing. Let me know what you think