Skip to content

Conversation

@khasinski
Copy link
Contributor

Since commit 9471b13 added MRB_TRY/MRB_CATCH to bigint.c for exception-safe cleanup, the file includes <mruby/throw.h> which requires C++ compilation when MRB_USE_CXX_EXCEPTION is defined.

Follow the same pattern as mruby-compiler to compile bigint sources as C++ when cxx_exception_enabled? is true.

Fixes: #6702

Since commit 9471b13 added MRB_TRY/MRB_CATCH to bigint.c for
exception-safe cleanup, the file includes <mruby/throw.h> which
requires C++ compilation when MRB_USE_CXX_EXCEPTION is defined.

Follow the same pattern as mruby-compiler to compile bigint sources
as C++ when cxx_exception_enabled? is true.

Fixes: mruby#6702
@khasinski khasinski requested a review from matz as a code owner January 13, 2026 10:08
@gemini-code-assist
Copy link

Summary of Changes

Hello @khasinski, 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 resolves a compilation error within the mruby-bigint gem by introducing conditional C++ compilation for its C source files. This ensures that the gem builds correctly when C++ exceptions are enabled, as the bigint.c file now relies on C++ exception handling mechanisms. The modification aligns the mruby-bigint build process with existing practices in other mruby components, improving overall build stability and consistency.

Highlights

  • Conditional C++ Compilation: The build process for the mruby-bigint gem has been updated to conditionally compile its C source files (core/**/*.c) as C++ when C++ exceptions are enabled in the build configuration (cxx_exception_enabled?).
  • Resolution of Compilation Issue: This change directly addresses a compilation issue where bigint.c includes <mruby/throw.h>, which necessitates C++ compilation when MRB_USE_CXX_EXCEPTION is defined, ensuring proper handling of exception-safe cleanup.
  • Build System Consistency: The implementation follows the established pattern used by mruby-compiler for handling similar C++ exception requirements, promoting consistency across the mruby project's build system.

🧠 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

@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 updates the build configuration for the mruby-bigint gem. It ensures that the gem's C source files are compiled as C++ when C++ exceptions are enabled in the mruby build. This change is necessary due to the recent addition of exception handling macros (MRB_TRY/MRB_CATCH) that require C++ compilation when MRB_USE_CXX_EXCEPTION is defined. The implementation is clean, follows existing patterns in the mruby build system, and effectively resolves the compilation issue. The change is well-scoped and looks good to merge.

@matz
Copy link
Member

matz commented Jan 13, 2026

The issue #6702 is addressed by 6b9e477 in different way from this PR. But thank you anyway.

@matz matz closed this Jan 13, 2026
@khasinski khasinski deleted the fix-bigint-cxx-exception branch January 13, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mruby-bigint doesn't compile in c++ project

2 participants