Matt Corallo

So what *is* the MSRV policy? Based on that comment it sounds like it's "sorry, you deal with it, we're not gonna think about it". In general I'm somewhat surprised...

Is it possible to provide an MSRV for *past* release patch versions? I realize this is talking about the latest version (which I missed above) where development wants to move...

We'll probably end up with a handful of followups to upstream stuff to `bitcoin-io`/drop our usage of `Cursor`/remove `no-std` features, but they can be in a followup.

Note that #3302 improves this a bit, even if it doesn't fix it.

Mmm, interesting, yea, that's nifty, thanks! We could probably do this by pushing the decision of how much to send over a channel into the scorer and then the router...

Cool! That's really related to #2547 (which is indeed exponential), which I'd love to iterate on if you have a suggestion for a great function. One further constraint here is...

Sure, a lookup table is a perfectly reasonable way to make most functions fast, as long as we're normalizing it against the bounds of the liquidity and not doing something...

Nice! After #2551 lands (hopefully this week), we should think about letting the scorer, rather than the router, make MPP splitting decisions. This would both simplify the router, letting us...

Personally I'm generally very much not a fan of formatters in that sometimes you want to do custom things for readability (eg if you want to manually align lines so...

This is blocked on either https://github.com/rust-lang/rustfmt/issues/4306 (maybe) or https://github.com/rust-lang/rustfmt/issues/4146 (hopefully), as we found in 425 that rustfmt just can't generate readable code for lots of things.