Replymessage unavailable
You’re absolutely right coroutines and GUIs are a match made in heaven, and for Qt, embracing coroutines is absolutely one of the most important steps toward modernizing the framework.
I completely agree that coroutines need to be lightweight and “green”, but it seems like achieving this would require either a massive rewrite of Qt’s core event loop or some extremely clever workaround. Neither approach seems straightforward.
Whether in C++ or Python, current third-party implementations feel clunky and lack elegance. What’s worse is that the Qt team doesn’t appear to prioritize this area, despite Qt’s existing async APIs (like Qt Concurrent and QFuture) drowning developers in boilerplate code. Even thread pools and manual threading end up tangled in signal/slot noise. Coroutines could wipe all that away with cohesive, linear-looking code—no more fragmentation. I genuinely hope we can push for this paradigm shift.🥹