We might not need to useNPY_LIST_PICKLE as when NumPy pickles a QuadPrecDType array:

• It saves the dtype (using ourreduce) (QuadPrecDType, ('sleef',))
• It saves the shape
• It saves the data,PyArray_ToString returns raw 128-bit bytes

StringDType needsNPY_LIST_PICKLE because:

• Its memory contains pointers to Python strings
• PyArray_ToString would just copy worthless pointer values
• So it uses_getlist_pkl to extract actual string objects

OurQuadPrecDType stores actual numeric values in memory, soPyArray_ToString works perfectly

hash implementation might require some careful handlinghttps://github.com/python/cpython/blob/20b69aac0d19a5e5358362410d9710887762f0e7/Python/pyhash.c#L87

I'll do this in a different PR and then we can close the#231

Why is the backend provided as an integer? A string literal might be a lot clearer, or if it has to be an int maybe we could add an int enum?

Why is the backend provided as an integer? A string literal might be a lot clearer, or if it has to be an int maybe we could add an int enum?

Internallybackendis defined as enum, we provide the friendly API for the user to add input as string. For the sake of static tools, IDE suggestions I think defining as enum might make sense maybe@jorenham can give some inputs here

I suppose you could doBackend: typing.TypeAlias = typing.Literal[1, 2], or maybe even anenum.IntEnum

@ngoldbaum a gentle reminder here for review

@SwayamInSync I'd appreciate it if you could give me more than a couple of days - especially over a weekend - before pinging me on PR reviews. I had your PRs on my to-do list.

@SwayamInSync I'd appreciate it if you could give me more than a couple of days - especially over a weekend - before pinging me on PR reviews. I had your PRs on my to-do list.

So sorry, I was working this weekend as well so slightly forgot the track of days :)

Merging this in