-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Sysinfo plugin compilation has been fixed for disabled multi_threaded feature #13964
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
Sysinfo plugin compilation has been fixed for disabled multi_threaded feature #13964
Conversation
6535452 to
64b49c9
Compare
|
Worth thinking about how this interacts with #13889 |
PR you metioned also tries solve throwing away result, but has amount of work for |
|
Looks like #13889, which I mentioned as better solution is not moving forward anymore |
|
Ping @JoJoJet, do you think we should wait for your PR? |
|
I can take some time this week to finish up that PR. I don't think it's very far from a mergeable state |
|
No longer blocked :) |
@alice-i-cecile we can close this PR, and mark #13957 as resolved by #13889 |
|
@bugsweeper have you verified that the compilation works with the given setup on |
Yes, I did ensured successfull compilation before asking for closing this PR |
Objective
multi_threadedfeature #13957 .multi_threadedfeature disabled, because single_threaded_task_pool::TaskPool::spawn returnsFakeTaskwhich can't contain future result, because it's just empty struct, but actualy for non wasm (forwasm32it indeed can't do better, because uses wasm spawn method which allows only futures which outputs only empty tuple) it spawns future, gets it's task, waits while executor finishes, and return nothing (FakeTask), throwing away _task with result!Solution
Testing
multi_threaded