3 ms·
True on the outset but you can partially control for it by e.g. implementing Future or Stream from the async runtime and have the implementor interact with the
by pdimitar 4y ago
True on the outset but you can partially control for it by e.g. implementing Future or Stream from the async runtime and have the implementor interact with the external resources. Then you can reshape unexpected or erroneous external state into Rust async errors, do retries, timeouts and whatnot.
I tried it, it helped. Doesn't solve everything for sure but I'll take any entropy decrease.
- pjmlp 4y agoAgreed, however that kind of effort is already quite different from how it gets usually sold, and on distributed computing world and multi-processes scenarios for security isolation purposes, what I care about are mostly external resources.
- pdimitar 4y agoWell, I suspect that for that to work properly we need an entirely new class of computing software, OS and maybe even hardware stack. Everything we do nowadays with distributed computing is, at best, writing a good networked app and then praying that it works and that it doesn't hit its 50 potential error states.