This actually makes the PeerData initialization independent from the
processor initialization. Next step is to move the initial proof
verification to the PeerData constructor as well.
Depends on D9419.
Fabien on Thu, Apr 15, 12:49.Authored by
This kinda have the right idea, but the execution is a problem. For as long as you do these in the various constructors, you must have objects at the end, and therefore you end up constructing possibly invalid objects, which is just bad design.
@PiRK started creating a factory method to construct the avalanche::Processor, why is this approach suddenly better?
Passing down the arg manager is a yes, but the execution isn't right.