Skip to content

Conversation

@junrushao
Copy link
Member

This PR makes __slots__=() for all subclasses of tvm_ffi.Object if not specified. Here's all the changes:

  • Rename the existing Cython class Object to CObject
  • Create a new Object whose metaclass is _ObjectSlotsMeta
  • Encourage inheriting from the new tvm_ffi.Object

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @junrushao, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant refactoring to the tvm_ffi.Object class structure, primarily to enforce the use of __slots__=() across its inheritance chain. This change is designed to optimize memory consumption and enhance the performance of attribute access for FFI objects by preventing the creation of instance dictionaries. The refactoring involves renaming the internal Cython base class, establishing a new Python-level Object class with a metaclass to manage __slots__ policy, and updating all dependent Cython modules to align with the new hierarchy and slot declarations.

Highlights

  • Refactored Object Hierarchy: The core tvm_ffi.Object class hierarchy has been refactored. The original Cython Object class is renamed to CObject, and a new Python Object class is introduced which inherits from CObject.
  • Enforced __slots__=(): A new metaclass, _ObjectSlotsMeta, is introduced for the tvm_ffi.Object class. This metaclass automatically enforces __slots__=() for all subclasses of tvm_ffi.Object if not explicitly defined, and prevents the inclusion of __dict__ in __slots__.
  • Optimized Attribute Access for Module: The Module class now explicitly uses __slots__ and implements a caching mechanism for function attributes in its __getattr__ method, improving performance for repeated attribute lookups.
  • Updated Cython Classes: Numerous Cython classes that inherit from Object (now CObject) have been updated to explicitly declare __slots__ = () and their type hints and casts have been adjusted to use CObject where appropriate.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a significant and valuable refactoring to enforce the use of __slots__ for all subclasses of tvm_ffi.Object. This is achieved by renaming the Cython Object to CObject and introducing a new Python Object with a metaclass that automatically adds __slots__ = (). This change will lead to considerable memory savings by preventing the creation of __dict__ for FFI objects.

The implementation is well-executed, with consistent updates across the codebase. The use of a metaclass with __instancecheck__ and __subclasscheck__ is a clever solution to bridge Python and Cython inheritance. The tests have also been updated to validate the new behavior.

I've identified a minor issue where some Cython classes have __slots__ = () added but retain a cdef dict __dict__ declaration. This seems contradictory to the goal of the PR and should be cleaned up to realize the full memory benefits.

@junrushao junrushao force-pushed the 2025-12-24/use-slots branch 2 times, most recently from a1f4bba to 3b94d14 Compare December 24, 2025 21:43
@junrushao junrushao changed the title feat: Restrict __slots__=() for all subclasses of tvm_ffi.Object feat: Restrict __slots__=() for subclasses of tvm_ffi.Object by default Dec 24, 2025
@junrushao junrushao force-pushed the 2025-12-24/use-slots branch from 3b94d14 to cc97e05 Compare December 24, 2025 21:47
@junrushao junrushao force-pushed the 2025-12-24/use-slots branch from cc97e05 to 7e5001d Compare December 24, 2025 21:52
@junrushao junrushao requested a review from tqchen December 24, 2025 21:52
@junrushao junrushao mentioned this pull request Dec 24, 2025
14 tasks
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