Karoy Lorentey

I'm fine with the `read(filling:)` name! (This operation is the reading equivalent to `writeAll`, so I would have been fine with `readAll(_:)` as well, for symmetry.) I don't think this...

> Does that mean the use site needs to first call stat to see how big the file is in order to not over-allocate the buffer? Also, would it back...

> Opaque is the default, and it's not as clear to me the benefits of making it not-opaque just to inline the loop into user code. I'm not sure if...

>> given that we provide writeAll, it seems silly not to also have the equivalent operation in the opposite direction. > > Yes, but read goes in the opposite direction...

> What should be Codable? I think we can make `SocketAddress.IPv4.Address`, `SocketAddress.IPv6.Address` and `SocketAddress.Port` codable. The addresses should probably serialize in String form. Codable for `SocketAddress.IPv4`, `SocketAddress.IPv6` and `SocketAddress.Local` may...

System calls its version of `mode_t` `FilePermissions`. If that's not the right name, that's unfortunate; but I don't think changing it would be a good idea at this point. There...

`S_IFMT`'s packed bits cannot be modeled well with an OptionSet like `FilePermissions` anyway -- I think System's wrapper struct for `struct stat` just needs to model the file format with...

(Popping in very quickly; I'll read through history and offer some more considered opinions soon.) My baseline expectation is that the APIs in #30 will be the starting point for...

One thing we could do is to put the combo overlay APIs into a separate build product that must be imported explicitly.

There is this whole family of address space-related functionality that we can't currently group under a specific type. This includes the anonymous flavor of `mmap`, as well as `munmap`, `msync`,...