make install, just run
make install-node-modules; the former builds native add-ons which you do not need to do for the feature you’re working on.
<toc>directives are namespace READMEs, which, for individual package contributions, shouldn’t need to be touched.
@stdlib/stats/base/dists/normal, which has various sub-packages, such as pdf, cdf, quantile, mgf, etc. Those are then packaged up and exposed via both a class implementation
@stdlib/stats/base/dists/normal/ctorand a namespace.
@stdlib/stats/base/dists/metalog/pdf? In which case, you don’t need to know anything about
<toc>directives, as those are not applicable for the README you’d create. Instead, you can just use the snippet linked to above or copy and paste a README for a PDF of another distribution and modify accordingly.
stdlib.ndarray(new Int32Array(d3.range(10))). Wouldn't that be easier than having to repeat the type and incurring a copy if it doesn't match?
stdlib.ndarray(new Int32Array(d3.range(10))). Wouldn't that be easier than having to repeat the type?
stdlib.arrayAPI: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/ndarray/array. This infers the dtype from the input buffer. The
ndarrayconstructor is a “lower level” API.
strided.ops.add(a.length, "int32", a, 1, "int32", a, 1, "int32", out, 1)throws
RangeError: invalid arguments. Number of indices must match the number of dimensions. ndims: 2. nargs: 1..