FrankReh

@Noah-Kennedy This is the kind of output I'm getting from the criterion benchmark with these changes. These times jive with what I was seeing with a different form of no_op...

I guess you have some issues with how I did it. I will have to pull your branch and see if you get the same kind of results, only better.

How async should handle close on drop seems to be one of the questions that comes up again and again, even for tokio. What drop are you referring to? Don't...

> So, with the off-runtime drop, I was referring to the semantics of, say, dropping a TcpListener. We could plan on a sync/std close for something like that, when the...

This starts as one commit over - #245 So 245 should be reviewed first.

[This](https://github.com/nrc/owned-buf/blob/main/src/lib.rs) may point to the std group wanting both `init` and `filled` in the owned buffer.

> Its interesting that it goes down the concrete type with destructor rather than trait object route. Presumably on code generation efficiency grounds. Yes. Would help for @Noah-Kennedy and @carllerche...

> Can't replace Fixedbuf, because it doesn't hold enough information to identify the registry. So could a FixedBuf and a sliced FixedBuf be used with non-fixed io operations like `read`...

An OwnedBuf is already 40 bytes and an OwnedCursor is 56. At what point is the size of the wrapper going to get in the way of being nice to...

And I think we could still use input from @Noah-Kennedy and @nrc to know whether adding a filled parameter, one way or another to our traits or eventually concrete types...