One of the barriers to HORTON 3.0 modularity is the presence of classes that permeate the entire project. One of these is the Matrix class.
We need to remove the matrix class and replace its functionality with either helper classes, or with named tuples. The appropriate choices will be case dependent. Each module will need to have the functionality removed and tested.
One of the barriers to HORTON 3.0 modularity is the presence of classes that permeate the entire project. One of these is the Matrix class.
We need to remove the matrix class and replace its functionality with either helper classes, or with named tuples. The appropriate choices will be case dependent. Each module will need to have the functionality removed and tested.