TYP: Allow passing floating, integer, and bool_ scalars to QuadPrecision.__new__

[jorenham]

This follows #199. See the added # NOTE for why we cannot annotate the array-like constructor cases.

I didn't see any mention of np.bool_ scalars in #199, only floating and integer ones. So I take it that QuadPrecision.__new__ does not accept np.bool_ instances then?

[SwayamInSync]

In [5]: issubclass(npq.QuadPrecDType().type, np.generic)
Out[5]: True

In [6]: npq.QuadPrecDType().type
Out[6]: numpy_quaddtype.QuadPrecision

In [7]: issubclass(npq.QuadPrecision, np.generic)
Out[7]: True

I think it is as Quadprecision already subclassing the np.floating

[jorenham]

Nice! I'll open a separate PR for that then.

[jorenham]

What does numpy_quaddtype.QuadPrecision.mro() return? (sorry I wasn't able to get it to build locally) Because there's a chance that there's some __subclasscheck__ trickery going on.

[SwayamInSync]

In [11]: npq.QuadPrecision.mro()
Out[11]: 
[numpy_quaddtype.QuadPrecision,
 numpy.floating,
 numpy.inexact,
 numpy.number,
 numpy.generic,
 object]

Building it requires the numpy build from source right now :)

[SwayamInSync]

So I take it that QuadPrecision.new does not accept np.bool_ instances then?

I think we should accept this right :) @jorenham I'll do the PR for this, you can assume it accept

cc: @ngoldbaum

[SwayamInSync]

@jorenham is this ready?
The new PRs I've added to address your comments and issues would not impact this?

[SwayamInSync]

Also for the part that QuadPrecision is type-safe (it subclassing np.generic)

[jorenham]

Yea this is fine to merge. I want to address the np.generic subclass stuff in a follow-up, since that will probably be a bit more involved

[SwayamInSync]

Cool thanks @jorenham merging this in