optout
optout
> But I'm curious why you need an ordering for elements of an unordered field? Ordering would have been needed for the tags in a bech32-encoded lightning invoice, each tag...
> So if you naively try to translate the old logic to the new one by just replacing types, you'll basically take an existing huge mess and kinda smear it...
Update: `Default` support has been added (https://github.com/rust-bitcoin/rust-bech32/pull/184), and `Ord` can be worked-around (needed only by `UnknownSemantics`).
Closing, no longer relevant, bech32 dependency is kept, was upgraded, was done with #3270 .
Rebased to current main, and current state of #3443 .
Rebased
Rebased; after #3513 many changes disappeared :)
Rebased, following channel phase #3418 . The channel manager part got much simpler!
Rebased up to 0216d7dfc27ea758f8d9a053d559b7fa096e4322 #3629 from joostjager/log-attribution-failures Mar 4 Cannot rebase past that, df6877445e3c3d05d772899bf12b9fe6178d08fd #3016 somehow breaks my rebaseing...