Johannes Weiss

@dnadoba API breakage is obvs expected, just FYI.

@swift-nio-bot test this please

> Thanks for the technical explanation! I'm glad a lot of thought went into this. > > Diving a bit deeper, I'm seeing a lot of the work is actually...

The workaround today is to open `/dev/null` or an extra pipe and close it straight away.

I'm totally open to adding such functionality if users think it helps them. The pipeline itself cannot be compile-time type safe because we support mutation but we can offer helpers...

> When it comes to "Swifty" APIs we should ask ourselves whether a ResultBuilder is an appropriate way to express this API. It's potentially hard for us to use one,...

@dnadoba Some other thoughts that I should probably leave here. - #1139 builds typesafe pipelines this way: `Handler1() Handler2() Handler3() Handler4() ...` which would only compile if the types are...

> check (using sample or so) if the EventLoop is blocked Just to comment that this is no longer true today, since #1887 we use a `DispatchQueue` to do the...

I don't _think_ this is correct for the two platforms we officially support. Both Linux and macOS have fixed-sized char arrays at the back of a `sockaddr_un`. We do (intentionally)...

the hack that we don't support is this one: ``` struct sockaddr_un *long_path = malloc(sizeof(*long_path) + 1024); *long_path = {0}; memcpy(long_path.sun_path, "/very/long/path/........") ``` if you hand that to NIO, it...