Alan Somers

> I would generally prefer to not be stuck on an old version of a dependency forever, even if it's test-only. If avoiding that requires `RawFd` to `BorrowedFd

@Darksonn @fkm3 I've finished updating mio-aio and its other downstream crates. It was hard plumbing I/O safety all the way through the stack! But I got it to work. If...

@oronsh the POSIX AIO pathway all works with Tokio 0.2. But I haven't worked out an interface that the maintainers find acceptable to use with Tokio 1.0. @Darksonn can we...

> Thank you @flakusha @asomers . > I guess the `posix aio` doesn't work with linux right? so it's only on mac? I looked into `tokio-file` crate. It's only for...

At that point, there wouldn't be any reason to use tokio-file. The ultimate goal, @oronsh should be for Tokio to include vectored methods that use std's blocking implementations by default...

That branch is incomplete, @oronsh . Notice that it doesn't even mention `read_at`. A complete PR would have many more SLOC. My preferred strategy is to implement this stuff bit-by-bit,...

matchers 0.2.0 is published now, which fixes the problem.

@ricardobranco777 what is the purpose of the `\0` separator? Should that initially be `''`? Currently, there is always an actual `\0` character printed at the beginning of the option list.

I have the same problem, though in my case I actually _did_ overflow an i64. A u64 gauge would be perfect for me. Or, failing that, if `IntCounter` had a...

For our my case, `f64` would be even worse. I have a counter, and I need to measure the difference between adjacent values, so `f64` would result in a big...