Servicide Swift

Vapour was e a big culprit for doing this. Because we had to leak a srinos implementation details to the client or to our api users, and so that they could write coats that we were leaking eventlt futures. Now, going forward, we can really kind of hide that way and make things just a single waiht. And swift neo as well, a, i don't want to speak for the swiftneo team, but at the moment, swift, no, it's kind of a library of two parts. It's both a concurrency library and an io library. But now that we have a single weight, there come future versions of swift ner, whenever