Skip to content

Rework issubclass #5867

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

Merged
merged 5 commits into from
Jun 29, 2025
Merged

Rework issubclass #5867

merged 5 commits into from
Jun 29, 2025

Conversation

youknowone
Copy link
Member

@youknowone youknowone commented Jun 29, 2025

Summary by CodeRabbit

  • New Features

    • Improved type and subtype checking for objects, providing more explicit and efficient checks.
    • Enhanced validation for class objects, aligning behavior more closely with standard Python.
  • Refactor

    • Unified and clarified logic for class and subclass checks, improving error handling and matching Python’s semantics.
    • Optimized subclass checking for single inheritance cases, reducing unnecessary recursion.

Copy link

coderabbitai bot commented Jun 29, 2025

Walkthrough

This change introduces explicit subtype and type identity checks for Python types in the VM, adding helper functions and methods for efficient MRO-based subtype checking. It also refactors class and subclass checking logic in PyObject, improving clarity, error handling, and alignment with CPython semantics, especially for single and multiple inheritance scenarios.

Changes

File(s) Change Summary
vm/src/builtins/type.rs Added MRO-based subtype helper, PyType::check, Py<PyType>::is_subtype, and check_exact methods for type checking.
vm/src/protocol/object.rs Renamed check_cls to check_class; added abstract_get_bases; rewrote abstract_issubclass with optimized single inheritance loop; updated recursive_issubclass and real_is_instance to use new checks and align with CPython errors.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant PyObject
    participant PyType
    participant VM

    Caller->>PyObject: real_is_instance(cls, vm)
    PyObject->>PyObject: check_class(vm, msg)
    alt cls is PyType
        PyObject->>PyType: is_subtype(other)
        PyType-->>PyObject: bool
    else cls has __bases__ (tuple)
        PyObject->>PyObject: abstract_get_bases(vm)
        PyObject->>PyObject: abstract_issubclass(cls, vm)
    end
    PyObject-->>Caller: result
Loading

Possibly related PRs

  • RustPython/RustPython#5855: Refactors and extends instance and subclass checking logic, including real_is_instance and union type support, closely related to this PR's enhancements to type and instance validation.

Poem

In the warren of types, I hop with glee,
Checking subtypes and classes, as swift as can be.
With MRO wisdom and exacting sight,
I leap through inheritance, making checks right.
From base to subclass, my logic is tight—
Rusty rabbit, coding through the night! 🐇


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b93bcb0 and 4e5007a.

📒 Files selected for processing (1)
  • vm/src/protocol/object.rs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • vm/src/protocol/object.rs
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: Check Rust code with rustfmt and clippy
  • GitHub Check: Run snippets and cpython tests on wasm-wasi
  • GitHub Check: Run snippets and cpython tests (windows-latest)
  • GitHub Check: Run tests under miri
  • GitHub Check: Run snippets and cpython tests (ubuntu-latest)
  • GitHub Check: Run snippets and cpython tests (macos-latest)
  • GitHub Check: Check the WASM package and demo
  • GitHub Check: Run rust tests (windows-latest)
  • GitHub Check: Run rust tests (macos-latest)
  • GitHub Check: Run rust tests (ubuntu-latest)
  • GitHub Check: Ensure compilation on various targets
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@youknowone youknowone merged commit 47a7a00 into RustPython:main Jun 29, 2025
12 checks passed
@youknowone youknowone deleted the issubclass branch June 29, 2025 05:28
@coderabbitai coderabbitai bot mentioned this pull request Jun 30, 2025
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