Sort out the class instantiation
climategadgets opened this issue · comments
Original code was written before dependency injection became commonplace. Need to update the behavior - it shouldn't be possible to change the object heritage once it's been instantiated.
Right now, there's a mess with calling init() from constructors causing all sorts of instantiation race conditions - there's no sensible solution other than a total separation of instantiation, initialization, and use.