srrrse
srrrse
Someone correct me if we don't guarantee this yet, but I think if you box the error, `Result`s will be subject to the NPO, and be 1 pointer in size....
@Yamakaky Have you tried implementing `From for Box`? `Box` is exempted from some of the normal orphan rules and so it might work. (Seems to work in playpen: https://is.gd/fjbjZS) Edit:...
Will do this week!
Agreed that this is just an abstraction for a datagram protocol.
I don't understand why a build script would be needed if you're using cfg accessible.
(NOT A CONTRIBUTION) I know this is an old issue but I think there's another perspective on this than what I've seen on the thread so far: the problem is...
(NOT A CONTRIBUTION) I see. That is a more complicated pattern than I initially thought. But the solution is to buffer the results (rather than the futures) and then concurrently...
(NOT A CONTRIBUTION) > The very root of the problem is that Buffered acts like the channel you suggest would - it limits the number of futures in flight, and...
(NOT A CONTRIBUTION) > Buffered does store the results of futures that have completed Sorry, you're right, I was thinking of BufferUnordered. But it only fills that buffer as futures...
My initial inclination is against doing something like this, but I could be convinced. There are a few barriers already against accidentally publishing: 1. The `cargo publish` command has no...