Skip to content

Try rational #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from
Draft

Try rational #1

wants to merge 14 commits into from

Conversation

rossbar
Copy link
Collaborator

@rossbar rossbar commented Apr 6, 2021

WIP: First attempt at rational dtype.

  • Type hierarchy: DTypeMeta vs. DType - why the base class
    for float64Unit?
  • What's the difference between PyArray_Descr and
    PyArray_DTypeMeta? Should a user dtype implementer have access to/ever use
    the latter?
  • Is a piecemeal approach feasible, i.e. can I provide a dummy
    castingimpl and create a viable dtype (that doesn't do anything).

rossbar added 14 commits April 2, 2021 10:03
Note: causes segmentation fault at interpreter exit due to
bad refcounting somewhere. Hopefully not relevant once new
dtype spec is in place.
 * Type hierarchy: DTypeMeta vs. DType - why the base class
   for float64Unit?
 * What's the difference between PyArray_Descr and
   PyArray_DTypeMeta? Should a user dtype implementor ever use
   the latter?
 * Is a piecemeal approach feasible, i.e. can I provide a dummy
   castingimpl and create a viable dtype (that doesn't do anything).
side note: fixes stack smashing error, now back to regular segfaults.
DType class is of type PyArray_DTypeMeta, which is not public.
Use PyObject for prototypes instead for now.
Forwards through errors from dtype creation at import time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant