data: withReverse{Reference,Contribution}List: factor commonality

This doesn't actually move the common behavior into e.g. devoted
component compositions - these two still mirror each other - but
it *does* isolate the differing behavior in terms of dependencies
that are computed uniquely but surrounded by identical
compositional steps.

This generally seems like a good fit for compositional subroutines,
but those aren't official yet. Meanwhile, this is still factored
much better than the previous implementation, and hopefully easier
to follow as well!

0 files changed, 0 insertions, 0 deletions