Athan

While the focus of the OP is centered around the main project repository, ideally whatever is done can also apply and be used for generating JSDoc documentation in standalone stdlib...

Note that the generation of HTML generation would likely entail the creation of a web frontend, with support for theming and integration with the main project documentation. Generated JSDoc documentation...

@Planeshifter May be good to flesh out this idea a bit more, perhaps with a link or two to example APIs found in other libraries/programming languages.

To reiterate, and as indicated in the OP, no methods should be added to the `ndarray.prototype`. An `ndarray` object is intended, and should remain, a minimal wrapper which simply describes...

@rreusser Agreed. Were a GSoC contributor interested in this idea, we'd need to spend some time up front sketching out the API design and probably doing a few POC packages.

For what is currently supported in stdlib, see https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/blas.

@glen-84 Much of the "cruft" that you linked to was never formally standardized. In particular, browsers attempted to provide non-standard APIs. What does make it into the standard is expected...

Prior art: https://github.com/n-riesco/ijavascript

Deno: - https://blog.jupyter.org/bringing-modern-javascript-to-the-jupyter-notebook-fc998095081e - https://deno.com/blog/v1.37 - https://docs.deno.com/runtime/manual/tools/jupyter

Prior art: https://github.com/yunabe/tslab