Athan

This PR has been superseded by #2349. Will go ahead and close. Thank you, @xaman27x, for your interest in stdlib.

What exactly would a "base" implementation do? Meaning, how feasible is it to actually make a "base" implementation? My sense is that we'd first need to create concrete implementations and...

There may be common logic around defining column widths (number of visible characters) and subsequent content truncation, or precision, but I'd be interested in seeing a concrete implementation first. Not...

I suppose we have some precedent for this with `@stdlib/plot/sparklines`. The `plot` namespace is generally a bit messy. Nevertheless, a `@stdlib/plot/table` namespace seems fine.

I am not sure it makes sense to distinguish `ascii` from `unicode`. In which case, I'd probably lean toward `@stdlib/plot/table/unicode` as the package name. And, while `python-tabulate` is a good...

@Snehil-Shah As a first step, I would not create a "base" implementation. First, create the Unicode/ASCII implementation with an emphasis on clear separation of concerns. You really won't know what...

For reference, when I wrote the sparkline packages, I started with concrete sparkline implementations and then extracted out the common components to allow for code reuse. I suggest following a...

Would you mind performing an `npm ls` on the package's node module dependencies? In particular, I am interested in knowing the installed mathjax version number. It is possible that somehow...

Rather than defining your own multi-dimensional array type, one option you could consider is directly using, and building on, existing primitives already available in other libraries. E.g., [`@stdlib/ndarray`](https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/ndarray/ctor). In principle,...

@eduardoleao052 Fair enough. If there isn't the goal of ecosystem interoperation, then creating a custom type for use in a walled garden is certainly sensible. This stated, if interoperation is...