2 ms·
This is really a problem for .NET itself. The pervasive availability of thread-static state is the only way async/await could really go wrong.
by naasking 10y ago
This is really a problem for .NET itself. The pervasive availability of thread-static state is the only way async/await could really go wrong.
- maxxxxx 10y agoThere is more that can go wrong. For example in a desktop app a button click finishes before the async code has been executed. The code looks like it's blocking but it isn't. I have seen that a few times now.