Strict checking for valid assignment locations in mutable matrices #32
Description
Currently, assigning to an invalid location (outside band or triangular component) in a mutable matrix will throw an assertion.
Should be able to configure via build setting at compile time:
strict asserts on assigning a value:
- in the lower triangular component of an upper-triangular matrix and vice versa
- outside the bandwidth of a band matrix
lazy assignment lets you assign anywhere in the matrix and invalidate state accordingly:
- symmetry
- bandwidth
- triangular component
This would also convert the internal representation to conventional if the symmetry/band/triangular property is violated.