You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the advantages of async code is it does not block threads. For example, in a UI application, writing async code will allow the UI thread not to be blocked by long operations. However, in the current implementation, an async pipeline will block the current thread.
See https://github.com/valentiniliescu/TestPipelinesAsync for an WinForms example. There are 3 buttons:
one that does a synchronous long operation
one that does a asynchronous long operation
one that does a long operation in an async pipeline
You can check that the async pipeline behaves more like the synchronous click - the UI thread hangs till the operation finishes (try to click on the text boxes, the UI is frozen).
The text was updated successfully, but these errors were encountered:
One possible solution would be to have an async collector result. The downside is the refactoring to async would not be as seamless. Also, not sure if the implementation would be feasible.
One of the advantages of async code is it does not block threads. For example, in a UI application, writing async code will allow the UI thread not to be blocked by long operations. However, in the current implementation, an async pipeline will block the current thread.
See https://github.com/valentiniliescu/TestPipelinesAsync for an WinForms example. There are 3 buttons:
You can check that the async pipeline behaves more like the synchronous click - the UI thread hangs till the operation finishes (try to click on the text boxes, the UI is frozen).
The text was updated successfully, but these errors were encountered: