Make launch functions pub #1288
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 am currently working on a project where I need to run server-side code concurrently with Dioxus Fullstack. However, I noticed that there is no way to reuse the Tokio runtime created in the launch function. As a result, the only option available to me right now is to spawn a new thread and runtime, which seems inefficient.
I propose making the launch functions public. This would allow developers like me to copy the launch function's code into our codebases and manipulate the Tokio runtime as needed, such as spawning new functions onto it. This change would provide more flexibility and efficiency in running concurrent server-side code.