Proof-of-concept tiny package like mathjs with mutable "typed functions" and module-based dependency tracking/"tree-shaking"
Go to file
Glen Whitney d95e5ad930 feat: Allow reconfiguration of an existing picomath instance
Keeps track of which operations depend on the configuration and
  invalidates them for lazy reconfiguration when the config changes.
2022-03-25 14:40:57 -07:00
complex feat: Allow reconfiguration of an existing picomath instance 2022-03-25 14:40:57 -07:00
generic feat: Invalidation and lazy reloading of implementations 2022-03-25 13:09:50 -07:00
number feat: Add complex numbers 2022-03-25 01:54:20 -07:00
test feat: Allow reconfiguration of an existing picomath instance 2022-03-25 14:40:57 -07:00
.gitignore feat: Initial core of picomath 2022-03-25 00:49:03 -07:00
LICENSE doc: Initial commit 2022-03-24 20:44:46 -07:00
README.md docs: Update README to reflect status 2022-03-25 03:11:37 -07:00
package-lock.json feat: Initial core of picomath 2022-03-25 00:49:03 -07:00
package.json feat: Initial core of picomath 2022-03-25 00:49:03 -07:00
picomath.js feat: Add complex numbers 2022-03-25 01:54:20 -07:00
picomathInstance.js feat: Allow reconfiguration of an existing picomath instance 2022-03-25 14:40:57 -07:00
poortf.js feat: Invalidation and lazy reloading of implementations 2022-03-25 13:09:50 -07:00

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.