3 ms·
Correct, there’s no actual problem here, just a potential performance pitfall, but that pitfall is no worse than a naive synchronous implementation would be. T
by hdevalence 4y ago
Correct, there’s no actual problem here, just a potential performance pitfall, but that pitfall is no worse than a naive synchronous implementation would be.
There’s no big problem here, just write code and run it. If it is a really big problem it will show up in a profiler (if you care enough about performance to care about this issue, you are using a profiler, right… right?)
- dcow 4y agoI guess you've never written async code. You can irreparably stall the entire program. I've done it. The person you're responding to is not correct in their analysis.