Carlos Scheidegger

It might be worth adding a warning to the user anytime an out-of-order (in the TimeSeries dimension) insertion happens. It's an easy mistake to make that triggers a 100x slowdown...

"Invalid Path Size"

2

I'm trying a new dataset, and during the build process, I get ``` terminate called after throwing an instance of 'std::runtime_error' what(): Invalid Path Size ``` I don't know if...

It would be a good idea to allow users to configure the cross-origin headers emitted by nanocube http servers. Right now we're hard-coding `"Access-Control-Allow-Origin: *"`, which means that if we...

One is badly needed :)

Our "core" query language is a conjunction of clauses across dimensions. This core language is good in that if the query is resolution-bounded, so is the time it takes to...

feat: add path to ImportMapError::UnmappedBareSpecifier

4

This improves the error message emitted in the case of an unmapped specifier, specifically adding the path of the relevant import map. Having the path information right there would have...

Sticky topics?

1

Are there any plans to support sticky topics?

I've been bitten by typing `Shade(x, y, z)` instead of `Shade.vec(x, y, z)`. We should either check for multiple parameters or actually just call `Shade.vec()` in case we get more...

We get literals like "NaN.0" which are nonsense.

I bought the kool-aid, might as well drink it.