adding asynchronous job tracking support for statusline - #9536
Closed
hazelwiss wants to merge 2 commits into
Closed
Conversation
Member
|
This is not feasible anymkee because with the event system jobs now get spawned as tokio tasks instead of being put in a futures unordered. You can't count them anymore. Background tasks are an implementation detail that often have nothing to do with system lands since tokio can easily hane millions of (sleeping) background tasks. Particularly with the new event system the number of background tasks increases a lot (and can cahnge based kn vsrious factors) but that has basically no impact on performance. The way I want to handle waiting on tasks is with something like #6436 |
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
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.
Adding a statusline option for displaying the amount of asynchronous jobs which are scheduled. I find myself wanting this information because currently, when working on large workspaces, certain operations take a long time to process and therefore being able to see whether or not the job was successfully scheduled could help so that you're not spending time thinking about how many unfinished write commands you have ongoing, or if you correctly opened the workspace symbol picker because it takes so long to open.