Matt Corallo 42ebf77415 Move Score into a scoring module instead of a top-level module ... Traits in top-level modules is somewhat confusing - generally top-level modules are just organizational modules and don't contain things themselves, instead placing traits and structs in sub-modules. Further, its incredibly awkward to have a `scorer` sub-module, but only have a single struct in it, with the relevant trait it is the only implementation of somewhere else. Not having `Score` in the `scorer` sub-module is further confusing because it's the only module anywhere that references scoring at all.		2021-11-16 20:58:37 +00:00
..
bin	[fuzz] Print the output of all failed test cases, not one test.	2021-05-20 21:18:35 +00:00
msg_targets	[fuzz] Swap mode on most messages to account for TLV suffix	2021-09-18 01:01:41 +00:00
utils	Persist ChannelMonitors after new blocks are connected	2021-10-20 00:06:17 +00:00
chanmon_consistency.rs	Provide payment retry data when an MPP payment failed partially	2021-10-30 01:53:19 +00:00
chanmon_deser.rs	Drop writer size hinting/message vec preallocation	2021-09-18 01:01:41 +00:00
full_stack.rs	Move Score into a scoring module instead of a top-level module	2021-11-16 20:58:37 +00:00
lib.rs	Fix a number of bugs in zbase32 and add a fuzzer which caught them.	2021-04-16 07:35:03 +02:00
peer_crypt.rs	Relicense as dual Apache-2.0 + MIT	2020-08-10 21:12:44 -04:00
router.rs	Move Score into a scoring module instead of a top-level module	2021-11-16 20:58:37 +00:00
zbase32.rs	Fix a number of bugs in zbase32 and add a fuzzer which caught them.	2021-04-16 07:35:03 +02:00