Mentioned by @skywhale in #53 (comment) CC @bschwind.
It would be certainly more locally consistent as the receive_timeout field is already private on purpose. It would cause some churn for crate users, but better sooner than later?
Note that Context is no longer user-constructible after merging #53.
Mentioned by @skywhale in #53 (comment) CC @bschwind.
It would be certainly more locally consistent as the
receive_timeoutfield is already private on purpose. It would cause some churn for crate users, but better sooner than later?Note that
Contextis no longer user-constructible after merging #53.