Johannes Weiss

https://github.com/swiftlang/swift-evolution/blob/main/proposals/0430-transferring-parameters-and-results.md will be useful to construct `NIOLoopBoundBox` with a non-`Sendable` value off EL. But the compiler isn't ready quite yet. This is a followup for #2753 (which allows `Sendable` values)...

`FileChunks` is an `AsyncSequence` but not `Sendable`. That makes it annoying to use in places.

ByteBuffer should have hex bytes initialiser / write method

9

This is pretty much a companion of #2447 / #2475. The aforementioned bugs/patches introduce the ability to get the hex dump from a `ByteBuffer` which is awesome. Next, I'd like...

macOS build broken (since Snippets)

4

``` /Users/johannes/devel/swift-nio/Snippets/NIOFileSystemTour.swift:89:37: error: 'valueForAttribute' is only available in macOS 10.15 or newer 87 | // Where supported, the extended attributes of a file can also be accessed, read, and modified:...

MessageToByteHandler never shrinks its buffer (it should!)

2

https://github.com/apple/swift-nio/blob/e2aef20375a9626b4ce3a32786a6626678e9f19c/Sources/NIOCore/Codec.swift#L748 NIO's `MessageToByteHandler` tries to reuse its existing `self.buffer` to save allocations. It doesn't however ever shrink that buffer. So if the user ever sends something super large, the buffer...

ByteBuffer: Investigate optimal allocation sizes (probably just under a power of two)

1

Currently, ByteBuffer always allocates in powers of 2 which makes sense. But many allocators have a small amount of overhead which means the actual space reservation might be even bigger,...

Rename and clarify the `body.collect(upTo:)` API which gets used in an insecure way all the time

1

We see code similar to this a lot ``` let expectedBytes = response.headers.first(name: "content-length").flatMap(Int.init) ?? 1024 * 1024 return Response(status: response.status, buffer: try await response.body.collect(upTo: expectedBytes)) ``` The above code...

``` warning: 'swift-nio-ssl': found 1 file(s) which are unhandled; explicitly declare them as resources or exclude from the target .build/checkouts/swift-nio-ssl/Sources/NIOSSL/PrivacyInfo.xcprivacy ```

[SR-9323] KeyPaths are quite slow

7

| | | |------------------|-----------------| |Previous ID | SR-9323 | |Radar | rdar://problem/52529589 | |Original Reporter | @weissi | |Type | Bug | Attachment: [Download](https://user-images.githubusercontent.com/2727770/164963044-daaa6692-c66d-47a3-b822-a02930633670.gz) Additional Detail from JIRA | |...

It'd be great to annotate the types with correct Sendable conformances.