Move `Score` into a `scoring` module instead of a top-level module 2021-11-chan-size-scoring
authorMatt Corallo <git@bluematt.me>
Fri, 12 Nov 2021 15:52:59 +0000 (15:52 +0000)
committerMatt Corallo <git@bluematt.me>
Tue, 16 Nov 2021 20:58:37 +0000 (20:58 +0000)
commit42ebf774155632b5656fd5820eb8c28d0003d9b6
tree59c02333f1480f3386c9cd9f19c24a67b7552164
parent9bec35ddde1750359c47b0a83f820ab7287cfd03
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.
fuzz/src/full_stack.rs
fuzz/src/router.rs
lightning-invoice/src/payment.rs
lightning-invoice/src/utils.rs
lightning/src/ln/channelmanager.rs
lightning/src/routing/mod.rs
lightning/src/routing/router.rs
lightning/src/routing/scorer.rs [deleted file]
lightning/src/routing/scoring.rs [new file with mode: 0644]
lightning/src/util/test_utils.rs