Add rfl::Commented, resolves #597#601
Conversation
Summary of ChangesHello @liuzicheng1987, 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 introduces the Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request simplifies an error message in ViewReader.hpp. However, the change removes helpful guidance for the user on how to resolve the error. My review includes a suggestion to restore the helpful information in the error message to improve the developer experience.
| stream << "Value named '" << _current_name_or_index | ||
| << "' not used. Remove the rfl::NoExtraFields processor or add " | ||
| "rfl::ExtraFields to avoid this error message."; | ||
| << "' not used."; |
There was a problem hiding this comment.
This change makes the error message less helpful by removing the proposed solutions for the user. The previous message explained that rfl::NoExtraFields was active and suggested either removing it or adding rfl::ExtraFields to the struct. This guidance is very useful for developers using the library.
Please consider restoring this part of the error message. If rfl::Commented (as mentioned in the PR title) provides another alternative, it would be beneficial to include that in the message as well.
| << "' not used."; | |
| << "' not used. Remove the rfl::NoExtraFields processor or add rfl::ExtraFields to avoid this error message."; |
No description provided.