Skip to content

Type Hierarchy (depends on UFunc dispatching simplification thoughts) #21

@seberg

Description

@seberg

If (and only if!) UFunc dispatching appears to be possible solely based on something like a safe casting type hierarchy!

Then it seems likely that an abstract hierary (hierarchy defined on AbstractDTypes) serves much less purpose. It may be unnecesssary to define it. At least it is likely unnecessary to define it based on isinstance, but should rather maybe be only defined based on can_cast (or whatever the alternative is).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions