Sebastian Berg

We can encode NA into the dtype, that is no problem. But I agree, there a couple of open questions around NA. NumPy could just support the NA part, in...

> The main implementation choice will use two arrays, one to hold the characters, and another to hold offsets pointing to the start of each element Presumably, this is a...

@mayalinetsky-kryon I did not follow the whole post, but if you know that you are dealing with indexing operations in NumPy, you should always use `dtype=np.intp`. This is a bit...

@leofang that seems just a problem with that specific implementation. I would expect it to be quite a lot faster on any hardware. (Less memory throughput and if `sqrt` is...

> We could make axis optional only in the case of 1D arrays Seems OK, since it is compatible with `None` as a default. But, is there much reason for...

@shoyer do you have an opion here? IIRC you were one of those arguing the most against a 3-way True/False/None switch. As to Chucks proposal, the question here is how...

@shoyer could you post that opinion at NumPy, because last time around, I feel you were one of the people arguing strongly against a 3-way "boolean" switch here.

Yeah, the next step would be updating NumPy and getting the deprecation going.

For the use-case of reading blobs from the buffer protocol, I prefer the `frombuffer` API. OTOH, I guess Dask cannot export buffers and it doesn't match well for a "reinterpret...

> Of course there is a need to support sliced array, which do not have the proper alignment. Yes, so why even discuss enforcing any alignment beyond the itemsize? Slicing...