don't make MainExecutor private/hidden #10
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I get that this is awkward and not a real solution (more of a proposal to discuss ideas, if wanted)
As somebody "new" looking to learn a bit more about
smol
and theasync-
package ecosystem, I found it awkward and not intuitive/friendly that MainExecutor isn't included insmol
orasync-executor
and instead hidden away here.What is an improvement that could be made either in this crate or smol / async-executor so that there is a more clear "default" implementation more robust than a single-threaded
block_on
?