> Frankly, I don’t think async code is leaky at all, and the ways that it does leak are largely due to library problems. Huh? One could argue the exact same in

> Frankly, I don’t think async code is leaky at all, and the ways that it does leak are largely due to library problems. Huh? One could argue the exact same in opposite direction - blocking code isn't leaky at all, just wrap it in a Future. And if doing that is difficult because of !Send data, then those are just "library problems". You could always just use a threadsafe library instead, right?