Skip to content

make read_one_alternative more general#485

Merged
liuzicheng1987 merged 2 commits into
getml:mainfrom
ftschindler:patch-1
Aug 27, 2025
Merged

make read_one_alternative more general#485
liuzicheng1987 merged 2 commits into
getml:mainfrom
ftschindler:patch-1

Conversation

@ftschindler
Copy link
Copy Markdown
Contributor

MSVC 17.14 did not pick up the move assignment here and was complaining about a missing copy assignment operator in std::optional. Using emplace fixes the issue for me.

I did not run the tests locally, please let mo know if you need any further information!

MSVC 17.14 did not pick up the move assignment here and was
complaining about a missing copy assignment operator in
std::optional. Using emplace fixes the issue for me.
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 @ftschindler, 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 addresses a compiler-specific issue encountered with MSVC 17.14, where the compiler was not correctly handling move assignment for std::optional, leading to a complaint about a missing copy assignment operator. The change modifies the read_one_alternative logic to use an emplace call instead of a direct move assignment when populating a std::optional result, thereby resolving the compilation error and improving compatibility across different compilers.

Highlights

  • Compiler Compatibility Fix: Replaced a direct move assignment (*_result = std::move(*res);) with an emplace call (_result->emplace(std::variant<AlternativeTypes...>{std::move(*res)});) within the read_one_alternative method in Parser_variant.hpp to resolve a std::optional related compilation error specific to MSVC 17.14.
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.

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.

Code Review

The change from move assignment to emplace is a good way to work around the MSVC compiler bug. I've suggested a small improvement to make the emplace call more direct and idiomatic, which should also be slightly more performant by avoiding the creation of an explicit temporary std::variant.

Comment thread include/rfl/parsing/Parser_variant.hpp Outdated
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@ftschindler
Copy link
Copy Markdown
Contributor Author

Hi @liuzicheng1987 @Urfoex, I'm calling you out directly as you're listed in https://github.com/getml/reflect-cpp?tab=readme-ov-file#the-team-behind-reflect-cpp. I've never contributed to reflect-cpp before, what is your process for considering contributions?

@liuzicheng1987
Copy link
Copy Markdown
Contributor

@ftschindler , if the checks pass, the contribution is something that we would be willing to maintain the code quality is good, we merge.

@liuzicheng1987 liuzicheng1987 merged commit 2860ce3 into getml:main Aug 27, 2025
133 checks passed
@liuzicheng1987
Copy link
Copy Markdown
Contributor

@ftschindler , thanks for your contribution!

@ftschindler
Copy link
Copy Markdown
Contributor Author

Great, thanks for accepting!

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