https://bugs.documentfoundation.org/show_bug.cgi?id=98955
--- Comment #2 from Stephan Bergmann <sberg...@redhat.com> --- So comphelper::ThreadPool spawns a fixed number of threads upfront, regardless of how many are actually ever needed? Sounds odd. Maybe std::async would be a more useful implementation to use. Not sure there's any support on any OS to determine such a concurrency parameter that would be deemed useful in the given scenario. But sure, if there is, sal looks like a logical place to put it. (I just want to avoid adding anything there that's already available anyway, like in the std::thread::hardware_concurrency case.) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
