Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Nov 22, 2025

Inverts version detection flags to default to enabled on modern compilers. Renames zerocopy-foo to no-zerocopy-foo in Cargo.toml, build.rs, source code, and .github/workflows/ci.yml. Ensures check_all_toolchains_tested.sh passes by syncing CI config. Verified unit tests on all affected toolchains.

Closes #2259

Inverts version detection flags to default to enabled on modern compilers.
Renames `zerocopy-foo` to `no-zerocopy-foo` in `Cargo.toml`, `build.rs`, source code, and `.github/workflows/ci.yml`.
Ensures `check_all_toolchains_tested.sh` passes by syncing CI config.
Verified unit tests on all affected toolchains.
@joshlf joshlf requested a review from jswrenn November 22, 2025 21:26
@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 version detection mechanism within the zerocopy crate. Instead of explicitly enabling features for newer compiler versions, the system now defaults to enabling features and uses no- prefixed flags to disable them for older, less capable toolchains. This change simplifies the configuration for modern compilers and ensures compatibility across various Rust toolchains, with corresponding updates to the CI pipeline.

Highlights

  • Inverted Feature Flag Logic: The build.rs script now emits no-zerocopy-foo flags when the Rust toolchain version is lower than a specified version, effectively enabling features by default on modern compilers and using the no- flags to disable them for older toolchains.
  • Renamed Configuration Flags: All zerocopy-foo flags in Cargo.toml, build.rs, and the source code have been systematically renamed to no-zerocopy-foo to align with the new inverted logic.
  • CI Configuration Update: The Continuous Integration (CI) pipeline, specifically the check_all_toolchains_tested.sh script and .github/workflows/ci.yml, has been updated to reflect these changes, ensuring continued compatibility and testing across various Rust toolchains.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/ci.yml
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 correctly inverts the version detection flags, which is a good improvement for maintainability. The changes are applied consistently across Cargo.toml, build.rs, and all affected source files. The logic for conditional compilation has been preserved correctly with the new inverted flags. I've reviewed the changes thoroughly and found no issues. Great work on this large-scale refactoring!

@joshlf joshlf enabled auto-merge November 22, 2025 21:28
@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.14%. Comparing base (f65c938) to head (94f4d2f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2804   +/-   ##
=======================================
  Coverage   88.14%   88.14%           
=======================================
  Files          20       20           
  Lines        5450     5450           
=======================================
  Hits         4804     4804           
  Misses        646      646           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jswrenn
Copy link
Collaborator

jswrenn commented Nov 24, 2025

What's the motivation here?

@joshlf
Copy link
Member Author

joshlf commented Nov 24, 2025

What's the motivation here?

See #2259

@joshlf joshlf added this pull request to the merge queue Nov 24, 2025
Merged via the queue into google:main with commit 738e3f2 Nov 24, 2025
98 checks passed
@joshlf joshlf deleted the invert-flags-build-rs branch November 24, 2025 21:54
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.

Consider reversing --cfg flags for feature detection

3 participants