* Fix#1902: typo in an example in the documentation
* Replace recursive calls in typed-functions with `this`-style calls
* Replace more recursive calls in typed-functions with `this`-style calls
* Refactor compareNatural to use this-style recursion
Co-authored-by: josdejong <wjosdejong@gmail.com>
* make dot product faster and correct for ℂ
* minor fixes
* added tests, fixed bugs
* add dot for sparse matrices
* make multiply(vec, vec) use dot
* add test for complex vectors
* added test for mul(vec, vec), removed one TODO comment
Co-authored-by: Jos de Jong <wjosdejong@gmail.com>
* fix qr and sign edge cases
qr() was throwing an error if the pivots of a matrix were zero.
This commit fixes that and ensures that the results are consistant
with wolfram alpha.
Whilst doing this I found a bug in complex.js, I have added a work
around but we should flag this upstream.
I also addressed the long standing concerns about assert statements
within the body of the qr function.
Fixes#1669Fixes#942
* further improvements to qr and sign
mainly fixing things I got wrong in previous commit
* add array test
* fix: remove only from tests and disallow
Uses mochas `--forbid-only` flag as advised by
https://github.com/standard/standard/issues/988
* Fixed unit base recognition and formatting for user-defined units
* Manually copied work from another branch
* Removed semicolons
* Replaced assert.equal with assert.strictEqual
* Added support for bignumber
* Replaced var with const
* chore(package): update standard to version 12.0.0
* update to new lint version with --fix
I believe this mainly adds whitespace to `{}`'s.
* Replace assert.equal with assert.strictEqual
This breaks a lot of tests which I will endevour to fix in the next
commits.
* Fix most errors due to assert.strictEquals
Some instances of `strictEquals` are replaced by `deepEquals`.
`toString` has been used to make some string comparisions explicit.
Tests will still fail untill #1236 and #1237 are fixed.
* Fix assertion erros due to -0
With node 10, assert.strictEqual no longer considers `0 === -0`.
I missed these first time round as I was using node 8.
* Put toString correct side of bracket
I was converting the constructor to a string rather
than the result of the computation. Oops.
* Fixed#1236: quantileSeq has inconsistant return
* Update package-lock
* Fixed#1237: norm sometimes returning a complex number instead of number
* Fix cli tests
* More changes for standardjs, and fixes in unit tests
