fix: don't call Args.add() with an integer

[EdSchouten]

The documentation for Bazel's Args states that standard conversion rules are only specified for strings, Files, and Labels. For all other types the conversion to a string is done in an unspecified manner, which is why it should be avoided.

Let's stay away from this unspecified behaviour by explicitly converting the precompile optimization level to a string before calling Args.add().

[gemini-code-assist]

Summary of Changes

Hello @EdSchouten, I'm Gemini Code Assist¹! 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 improves the robustness and predictability of the build process by ensuring that arguments passed to Bazel's Args.add() method adhere strictly to documented type conversion rules. By explicitly casting an integer value to a string, it eliminates reliance on undefined implicit conversions, thereby preventing potential runtime issues and making the code more resilient to future Bazel updates.

Highlights

• Bazel Args.add() Type Safety: Ensures that the precompile_optimize_level attribute is explicitly converted to a string before being passed to Args.add(), aligning with Bazel's documentation which specifies standard conversion rules only for strings, Files, and Labels, thus preventing reliance on unspecified implicit conversions for integers.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

[gemini-code-assist]

Code Review

The pull request addresses an issue where the Args.add() method was being called with an integer value, which is not explicitly supported according to Bazel's documentation. The change converts the precompile_optimize_level attribute to a string before passing it to Args.add(). This ensures that the argument is handled in a predictable manner, avoiding unspecified behavior.