Johannes Weiss

Don't think this is reasonably (without incurring double-index checking etc which is what you'd get if you'd back it by `Slice`) possible because `Deque` isn't self-slicing but `CircularBuffer` is. FWIW,...

@FranzBusch Well, `CircularBuffer`'s API is self-slicing. `Deque` isn't and that's why you can't keep the API and implement it on `Deque` efficiently. You could back it with `Slice` but this...

@simonjbeaumont / @Lukasa what are the thoughts w.r.t. Swift System having an OS-dependent API?

@ddunbar any input here? The 2.0 development work will start shortly

We could also trial a few implementations of this in a new `NIOExtrasWhatever` package. Not sure if we should add a new operator to NIO, it may have source breakage...

Finally! (almost)

We could/should? Add an `append` mode? @Davidde94 Two random things: 1) please avoid `NIOAny(...)`, use `self.wrapInboundOut(...)` to make sure your types are correct 2) you should close the file in...

An ELF does guarantee ordering and therefore happens before: - A given ELF runs one callback after the other (it doesn't actually currently ask the EL to do, it just...

Sounds good. Although > where tasks that have the same deadline must execute in the order they were submitted to the event loop we don't do that right now. If...

Agreed.