3 ms·
Go seems to have solved the IO problem, but what about the general asynchronous issue? How do you handle calling a function several thousand times on dozens of
by Guvante 12y ago
Go seems to have solved the IO problem, but what about the general asynchronous issue? How do you handle calling a function several thousand times on dozens of threads and combine the results?
- rco8786 12y agoIs there any reason you couldn't just spin up so goroutines to do this?
- Guvante 12y agoTelling a hundred threads to do work is easy, figuring out how to sync all of the answers is the hard part. I am not saying you can't pull it off, but the proposed solution doesn't simplify the complex part of those operations.
- the_af 12y agoHow does Go solve "the IO problem"? (Probably what I want to ask is: which IO problem does Go solve? It can't be the one about purity and side-effects, and if it doesn't solve that...)
- Guvante 12y agoHow do you do IO without stalling your whole program while it accesses the data, specifically the fact that the asynchronous call is terminated in your main loop, not where you are accessing the IO itself.