Since C++20 supports constexpr std::string, we can make ProxyAccessorBase(const std::string& _key) constructor constexpr.

Oct 17 '24 14:10 timadye

📊: Physics performance monitoring for e547cc414cf997f9d62bf1e226e42d6d7cac5031

Full contents

physmon summary

Oct 17 '24 16:10 github-actions[bot]

Makes sense. There's one unit test failure on macOS related to an unused variable.

Oct 17 '24 20:10 paulgessinger

Makes sense. There's one unit test failure on macOS related to an unused variable.

So the warning is here:

/Users/runner/work/acts/acts/build/Tests/UnitTests/Core/EventData/TrackContainerComplianceTests.cpp:77:36: error: unused variable 'caccNMeasuements' [-Werror,-Wunused-variable]
  ConstProxyAccessor<unsigned int> caccNMeasuements("nMeasurements");

Indeed, that variable is not used, because it is just used to check that you can't modify through a ConstProxyAccessor. I don't understand why this warning wasn't always there, and only appears now this constructor is constexpr.

That aside, do you have any ideas on how to fix this?

Oct 18 '24 16:10 timadye

@timadye maybe

diff --git a/Tests/UnitTests/Core/EventData/TrackContainerComplianceTests.cpp b/Tests/UnitTests/Core/EventData/TrackContainerComplianceTests.cpp
index 636b30bff5..731f9e01a4 100644
--- a/Tests/UnitTests/Core/EventData/TrackContainerComplianceTests.cpp
+++ b/Tests/UnitTests/Core/EventData/TrackContainerComplianceTests.cpp
@@ -75,6 +75,7 @@ ACTS_DOES_NOT_COMPILE_SUITE_BEGIN(BuildFromConstRef)
   (void)t;
 
   ConstProxyAccessor<unsigned int> caccNMeasuements("nMeasurements");
+  static_cast<void>(caccNMeasuements);  // suppressed unused warning
   ACTS_DOES_NOT_COMPILE_BEGIN(ConstAccessorMutate)
   caccNMeasuements(t) = 66;
   ACTS_DOES_NOT_COMPILE_END()

Oct 24 '24 08:10 paulgessinger

The macos build failure looks like an unrelated configuration problem (XercesC 3.2.5 instead of 3.3.0). Hopefully this can be fixed soon and we can see if the last update fixes the warning.

Oct 25 '24 11:10 timadye

In principle there should be a fix for this already. Maybe it's not merged yet

Oct 25 '24 17:10 paulgessinger

@AJPfleger I think this is waiting for your approval, if you do approve. Thanks!

Nov 05 '24 13:11 timadye

[!IMPORTANT]

Review skipped

Auto reviews are limited to specific labels.

:label: Labels to auto review (1)

coderabbit

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json