Skip to content

Chore update bolos-derive#51

Merged
abenso merged 3 commits intomainfrom
chore/update
Aug 20, 2025
Merged

Chore update bolos-derive#51
abenso merged 3 commits intomainfrom
chore/update

Conversation

@abenso
Copy link
Copy Markdown
Collaborator

@abenso abenso commented Aug 19, 2025

Removed proc-macro-error

Copy link
Copy Markdown

@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.

Summary of Changes

Hello @abenso, 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 primarily focuses on updating the bolos-derive crate's dependencies and adapting its procedural macros to these changes. The most significant change is the removal of the proc-macro-error crate, along with a major version upgrade of the syn crate from 1.x to 2.x. These updates ensure the derive macros remain compatible with the latest Rust ecosystem tools and simplify the dependency tree.

Highlights

  • Removal of proc-macro-error: The proc-macro-error dependency has been completely removed from the project, simplifying the dependency graph and reducing the overall footprint.
  • Syn Crate Upgrade: The syn crate has been upgraded to its major version 2.x, which required adapting existing procedural macro logic to the new API.
  • Dependency Updates: Other key dependencies including quote, proc-macro2, and convert_case have been updated to their latest compatible versions.
  • Refactored Error Handling: Error handling within the procedural macros has been refactored to use standard Rust panic! calls instead of the proc-macro-error specific functions.
  • API Adaptation for Syn 2.x: Adjustments were made across enum_init.rs, lazy_static.rs, and utils.rs to align with the API changes introduced by syn 2.x.
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
Copy link
Copy Markdown

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@chcmedeiros chcmedeiros self-requested a review August 20, 2025 08:35
@abenso abenso merged commit 7726cc0 into main Aug 20, 2025
2 checks passed
@abenso abenso deleted the chore/update branch August 20, 2025 11:22
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.

2 participants