Conform README and file layout #38

New issue

Open

opened 2025-12-12 17:03:17 +00:00 by glen · 0 comments

glen commented

2025-12-12 17:03:17 +00:00

Owner

Although the file layout described in the README and the current actual layout are close, they don't fully align. For example:

There is no builtin directory as described; boolean is at the top level.
There is a vector directory that primarily deals with Arrays. By the README, there should be an Array (or array or something) type in builtin/collection. Should vector just be renamed Array or array, and moved to that location? Or is it not what we want for the implementations for the builtin JavaScript Array type? If not, do we need two nanomath (mathjs) types? In mathjs 15 we have Array and (Dense)Matrix; is vector actually a prototype for (Dense)Matrix? I mean, I think it was named and located to be sort of agnostic between the two, but this needs to be decided and we need to document how things will be arranged and proceed that way.

There may well be other differences. They need to be decided on, and the README and the actual code should completely conform with each other.

Although the file layout described in the README and the current actual layout are close, they don't fully align. For example: * There is no builtin directory as described; boolean is at the top level. * There is a vector directory that primarily deals with Arrays. By the README, there should be an Array (or array or something) type in `builtin/collection`. Should `vector` just be renamed Array or array, and moved to that location? Or is it not what we want for the implementations for the builtin JavaScript Array type? If not, do we need two nanomath (mathjs) types? In mathjs 15 we have Array and (Dense)Matrix; is vector actually a prototype for (Dense)Matrix? I mean, I think it was named and located to be sort of agnostic between the two, but this needs to be decided and we need to document how things will be arranged and proceed that way. There may well be other differences. They need to be decided on, and the README and the actual code should completely conform with each other.