David Nadoba

observing disposed events

1

Hey, Is it possible to materialise disposed events too? The only way I could find to observer disposed events of a signal is using the [`on(event:failed:completed:interrupted:terminated:disposed:value:)`](https://reactivecocoa.io/reactiveswift/docs/latest/Classes/Signal.html#/s:13ReactiveSwift6SignalC2on5event6failed9completed11interrupted10terminated8disposed5valueACyxq_GyAC5EventOyxq__GcSg_yq_cSgyycSgA3RyxcSgtF) method. Thanks 🙏 David

Flaky test: `NIOPOSIXTests.EventLoopTest.testCancelledScheduledTasksDoNotHoldOnToRunClosure()`

1

I have seen it fail in CI and locally a couple of times now. It is also reliably reproducible if run repeatedly after ~500-2000 iterations. https://github.com/apple/swift-nio/blob/712e207f2621efd710576f3389d7bae361f46ae2/Tests/NIOPosixTests/EventLoopTest.swift#L807-L831 I have played a...

### Motivation: We want to incrementally comply with the strict sendability checking rules. ### Modifications: Move `ByteBuffer` allocation to thread modifying buffer by moving the mutable variable into the sendable...

Many methods on `EventLoop`, `EventLoopFuture` and `Scheduled` take an escaping function type as an argument. Most of these function types do now need to conform to `Sendable` because the function...

Adopt `noasync` for `Lock.lock()` and `Lock.unlock()`

4

Mark `Lock.lock()` and `Lock.unlock()` as not available from asynchronous context. ### Motivation: From [SE-0340 (Unavailable From Async Attribute)](https://github.com/apple/swift-evolution/blob/main/proposals/0340-swift-noasync.md#introduction): > The Swift concurrency model allows tasks to resume on different threads...

allocations might have changed for nightly build

Deprecate unsafe methods for adding/removing non-`Sendable` `ChannelHandler`s

6

### Motivation: `ChannelHandler`s are not required to be thread-safe and we need to assume they can only be used on their `Channel`s `EventLoop`. ### Modifications: - deprecate method which take...

It looks like requiring `ChannelOption.Value` to conform to `Sendable` is a source breaking change e.g. our own `RecvAllocatorOption` no longer compiles as the `RecvByteBufferAllocator` protocol wasn't required to be `Sendable`....

and `.get()` only available if `Value` is `Sendable`: ```swift extension EventLoopPromise: Sendable where Value: Sendable { } extension EventLoopFuture: Sendable where Value: Sendable { } extension EventLoopFuture where Value: Sendable...

Type-safe Pipeline

6

Hi everyone, I have played around with a type-safe Pipeline Builder by using phantom-types. It makes use of the associated types from `ChannelInboundHandler` and `ChannelOutboundHandler` to guarantee that handlers have...