Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Jan 24, 2026

Replace calls to Ptr::transmute with calls to transmute_with, which
accepts a CastExact parameter to specify the cast at the call site.


Latest Update: v4 — Compare vs v3

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v3 v2 v1 Base
v4 vs v3 vs v2 vs v1 vs Base
v3 vs v2 vs v1 vs Base
v2 vs v1 vs Base
v1 vs Base

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @joshlf, 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 refactors the type casting mechanism within the transmute crate by moving from an implicit Ptr::transmute to a more explicit transmute_with method. This change enhances clarity and type safety by requiring developers to specify the exact casting behavior (sized or unsized) at the point of use. Concurrently, it simplifies the codebase by removing several SizeEq trait implementations and the macro previously used to define them, indicating a consolidation or re-evaluation of how type size equality is managed.

Highlights

  • Explicit Type Casting: Replaced calls to the generic Ptr::transmute method with transmute_with, which explicitly accepts CastSizedExact or CastUnsized parameters to specify the casting behavior at the call site.
  • Removal of SizeEq Implementations: Removed several explicit impl_size_eq! macro calls for fundamental types such as bool, char, str, and NonZero variants, streamlining the type system's handling of size equality.
  • Macro Refactoring: The impl_size_eq! macro definition itself was removed from src/util/macros.rs, indicating a shift away from its usage for defining SizeEq traits.
  • New Cast Type Imports: Imported CastUnsized and CastSizedExact from crate::pointer::cast to support the new explicit casting mechanism.

🧠 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 is a good refactoring. It replaces the impl_size_eq! macro with more explicit calls to transmute_with, specifying the cast type directly. This improves code clarity and maintainability. The changes are applied consistently, and the correct cast types (CastSizedExact and CastUnsized) are used where appropriate. I see no issues with this change.

@joshlf joshlf force-pushed the Gbef390739b3d30f77bab67b5336a922b7a8cfb48 branch from 874ac1a to 6e86abb Compare January 24, 2026 17:19
Replace calls to `Ptr::transmute` with calls to `transmute_with`, which
accepts a `CastExact` parameter to specify the cast at the call site.

gherrit-pr-id: Gbef390739b3d30f77bab67b5336a922b7a8cfb48
@joshlf joshlf force-pushed the Gbef390739b3d30f77bab67b5336a922b7a8cfb48 branch from 6e86abb to fde6f62 Compare January 24, 2026 17:40
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