Cleanup and Verification through unit tests

[akielaries]

Aim to write unit tests for every method we have created so far

Cleanup: Use codacy reports and the cppcheck reports for cleanup on duplicate code. probably want to do some function renaming

[akielaries]

Step thru each module and verify implemented methods work via unit tests. After verification focus on the methods/code blocks that are reused (for example I need to create some vector operations on top of the existing matrix operations we have so far) and clean those bits up. Next, focus on the static analysis reports that are screaming errors about unused vars, functions, unsafe comparisons, etc.

[akielaries]

107 #108 are all related to this cleanup effort. for now:

• Unit test eigen, linsys, svd, and tensor files in linalg module
  • also ensure these need to be classes and verify OOP parts
• Unit test optimization methods and verify OOPness
• Create a vector class in the linalg module. Already have matrix methods but vector methods will be needed as well

There's a ton of work to be done so focus on the basics for now:

1. Wrap up an implementation, test/verify it, move onto the next thing
2. Compilation warnings, static analysis errors, code coverage warnings, bad OOP principles, benchmarking, etc are okay for now, this will be a post v1.0.0 release fix
3. Focus on core building blocks in math not applications

Immediate work:

1. Test and verify the following
   • linalg : eigen, svd, tensor, linsys
   • optim: quasi, function
2. Add linalg vector operation methods (intrins too)
3. Brainstorm additional items to add to the linalg, optim, and stats modules

[akielaries]

This is being separated into different issues