On Fri Nov 28 19:47:23 2025 +0000, Paul Gofman wrote:
And IIRC in windows.speech case the app motivated 84cd975748b8609feb19d9083f6486ebf0720461 doesn't even do anything to wait for the async result and proceedes to GetResults() at once. Introducing unndeeded async handling will be breaking such things.
Well, idk. IMO it's not a good thing to spread semi-stubbed async implementations around when they are all supposed to be implemented based on some common templates.
If our shared code isn't capable of creating completed asyncs maybe it should be added, but it should probably be added everywhere and given the number of duplicates already that doesn't sound very exciting.
In this particular case I don't think we consider Win10 as an old and unsupported Windows version already, and so making the async go through the threadpool seems acceptable to me.