Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed a should from Exception.h #43

Closed
wants to merge 1 commit into from
Closed

Conversation

Iximiel
Copy link
Owner

@Iximiel Iximiel commented Dec 22, 2023

Description

At first look this may look like an aestetic change.
But I encoundered a case i which the if (!(test)) plumed_error() << PLMD::Exception::Assertion(#test), the plumed_dbg_massert macro expansion with NDEBUG, is not optimized away, and this patch I think is the least invasive thing to do:

if constexpr(false) is guaranteed to be evaluated at compile time, so that the rest of the line is ignored.

I think helps in improving the code optimization after inlining a function, at least that is what I think it happened in my case

Target release

I would like my code to appear in release 2.10/2.9 (this is a single commit, it can be easily rebased on the 2.9)

Type of contribution
  • changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
  • changes to a module not authored by you
  • new module contribution or edit of a module authored by you
Copyright
  • I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.
  • the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.
Tests
  • I added a new regtest or modified an existing regtest to validate my changes.
  • I verified that all regtests are passed successfully on GitHub Actions.

@Iximiel Iximiel closed this Dec 22, 2023
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.

1 participant