Proof-of-concept tiny package like mathjs with mutable "typed functions" and module-based dependency tracking/"tree-shaking"
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Glen Whitney 2c1b6c3364 docs: Update README to reflect status 1 year ago
complex feat: Selective loader that extends all/only existing number methods to complex 1 year ago
generic feat: Initial core of picomath 1 year ago
number feat: Add complex numbers 1 year ago
test feat: Selective loader that extends all/only existing number methods to complex 1 year ago
.gitignore feat: Initial core of picomath 1 year ago
LICENSE doc: Initial commit 1 year ago
README.md docs: Update README to reflect status 1 year ago
package-lock.json feat: Initial core of picomath 1 year ago
package.json feat: Initial core of picomath 1 year ago
picomath.js feat: Add complex numbers 1 year ago
picomathInstance.js feat: Add complex numbers 1 year ago
poortf.js feat: Selective loader that extends all/only existing number methods to complex 1 year ago

README.md

Proof of concept for a JavaScript Computer Algebra System

An instance of the system will be an object whose property names are the operator names and whose property values are constant mutable function objects that can have new behaviors added to them.

Calling the system on a property name and 0 or more implementations creates that operator if it doesn't exist and adds the implementations to it, and returns the function object for that name. Thus, it is easy for modules to obtain handles to operations they depend on, and to create/extend an operation (typically just one per file at the moment).

Multiple different instances can coexist and have different collections of operations. Moreover, only the source files for the operations actually desired are ever visited in the import tree, so minimizing a bundle for a specific subset of operations should be quite straightforward.

Hopefully the test cases, especially test/_picomath.js and test/custom.js, will show this off in action.

Note that 'subtract' is implemented as a 'generic' operation, that depends only on the 'add' and 'negate' operations (and so doesn't care what types it is operating on).

This core could be extended with many more operations, and more types could be defined, and additional sub-bundles like number/all.js or clever conditonal loaders like complex/extendByComplex could be defined.

Hopefully this shows promise.