Skip to content

Implement the mro_lookup primitive #3

Description

@omelancon

Naming class_getattr is an historical mistake since it takes an object, not a type, as first argument. Not having a primitive to execute a lookup directly on a type has become a problem in #2.

We should implement a mro_lookup primitive. Doing class_getattr could then be written as mro_lookup(type(x), "__method__"). This is both more expressive and more accurately named.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions