Would you consider relaxing this requirement? š
Certainly itās good to encourage the use of a typed array here, say through documentation and examples, but I donāt anticipate the implementation would require that is the input is a typed array (e.g., I donāt think weād need to call coords.subarray). So it seems reasonable to allow anything array-like as input.
In particular, itās nice if you already have a flat plain array [x0, y0, x1, y1, ā¦] from some other library, and you arenāt forced to copy that array into a Float64Array to compute the Delaunay triangulation.
Would you consider relaxing this requirement? š
Certainly itās good to encourage the use of a typed array here, say through documentation and examples, but I donāt anticipate the implementation would require that is the input is a typed array (e.g., I donāt think weād need to call coords.subarray). So it seems reasonable to allow anything array-like as input.
In particular, itās nice if you already have a flat plain array [x0, y0, x1, y1, ā¦] from some other library, and you arenāt forced to copy that array into a Float64Array to compute the Delaunay triangulation.