Maximilian Roos

> We can easily raise if dtype is provided and ask them to use another "engine" Yes or to convert first (albeit requires a copy)

One question out of https://github.com/numbagg/numbagg/pull/128: To what extent do we want to convert types? Currently we always have the same input type as output type... ...except for `bool` which we...

This is somewhat downstream of #121. There's a bullet tucked away there "Always keep types — current state (except for bools...)" The current state is that we maintain types, apart...

Yes, good idea. IIUC this would help where there's a multi-dimensional output. Otherwise it's a single allocation anyway...

For transparency — I'm pushing these off for the moment. We're already 2x faster than pandas, and so we can wait until we have more adoption before adding optimizations. (Though...

I'm just trying out Dance, and hitting this. This might be a basic question — but how does vscodevim succeed at this?

> I switched to the "Unicode Hex Input" The problem with this is that it seems to be QWERTY only...

Hope it's OK to come back to this > I'm not even sure whether there are commands in Vim that use `Alt+I` or similar bindings (that don't work on Mac)....

> Update: activating the VSCode setting `terminal.integrated.macOptionIsMeta` fixes the problem for me. I can continue using a key layout with special characters mapped on Alt/Option, and it works in the...

This looks awesome @andreynering ! From my perspective — albeit limited — if an early version would mount a volume of the local path, and allow passing some flags, that...