David Nadoba

We could also deprecate the conformance and add two views to it, `ordered` and `unordered`, and only conform the views to Equatable/Hashable.

Any progress on this topic?`EventLoopGroupManager` looks actually really good! Maybe we can just move it into swift-nio-extras so we don't need to copy & past it.

@weissi FYI: nightly failure is expected because of a compiler issue https://github.com/apple/swift/issues/60797

Can you try connection to `https://apple.com` using `URLSession` instead of `AsyncHTTPClient` to see if this is a general networking error: ```swift import Foundation let (data, response) = try await URLSession.shared.data(from:...

I run into a similar issue with multiple trailing closures but for the `vertical_parameter_alignment_on_call` rule: ```swift PreviewView( previewLayout: .fitWidth(360) ) { SomeView() } update: { $0.update(data: data) } ``` Which...

It will still be possible to call `noasync` methods in async context indirectly. You will however need to wrap them in another function/closure like this: ``` _ = { lock.lock()...

Is this really a bug? I think not and we should keep the current behaviour because ### 1. It introduces invalid state transitions This would break the general Promise/Future contract...

We could also add an async `modify(_:)` method which takes a closure which takes `SynchronousOperations` as an argument: ```swift extension ChannelPipeline { @available(macOS 10.15, iOS 13, tvOS 13, watchOS 6,...

> One other thing (that I'm probably not recommending) which would allow us to keep the same syntax is > > ``` > func addHandler(_ handler: @Sendable @autoclosure () ->...

Are you on a Mac with an M1?