Skip to content
Snippets Groups Projects
  1. Jan 12, 2021
  2. Jan 11, 2021
  3. Jan 10, 2021
  4. Jan 08, 2021
    • Andrii Verbytskyi's avatar
      Try to have constcorrect... · 75a4367d
      Andrii Verbytskyi authored and Vakhtang Tsulaia's avatar Vakhtang Tsulaia committed
      Try to have constcorrect InnerDetector/InDetValidation/InDetRecStatistics/src/InDetRecStatisticsAlg.cxx
      75a4367d
    • Nils Krumnack's avatar
      fix all compiler warnings for AnalysisBase on latest MacOS · 602b780a
      Nils Krumnack authored
      New compiler, new set of warnings...
      
      The main theme here is that clang now checks for range-based for loops
      whether it introduces unneeded temporaries, i.e. if the user asks for
      a reference for the loop variable, but the iterator doesn't return a
      reference or a reference of a different type, or conversely if the
      user asked for `const auto`, but could have been `const auto&`.
      
      In practice that usually hits us as:
      ```
      for (const auto& jet : jetContainer)
      ```
      which should be:
      ```
      for (const auto *jet : jetContainer)
      ```
      
      Also a couple of places like this (which miss the `const` qualifier on
      the first template parameter):
      ```
      std::map<std::string,std::string> stringMap;
      for (const std::pair<std::string,std::string>& stringPair : stringMap)
      ```
      
      For the most part I just replaced the loop variable type with what
      seemed correct.  In a few places I put explicit comments as to why I
      chose the type.
      
      Also a fair number of warnings for unused member variables in various
      packages.  Since I am not an expert on any of these packages and this
      can point to an actual bug, I commented out all unused variables and
      added a comment for actual experts to check and remove.
      
      I removed a couple of checks for `this != nullptr` which were
      originally introduced to check whether the user called a member
      function via a null pointer.  However those checks are `assert`-based,
      so with cmake they won't be included when the user calls them from a
      release, making this check mostly useless.
      
      There some other warnings I fixed in the process that should hopefully
      be self-explanatory.
      602b780a
  5. Jan 07, 2021
  6. Jan 06, 2021
  7. Jan 05, 2021
  8. Jan 04, 2021
  9. Dec 25, 2020
  10. Dec 23, 2020
  11. Dec 22, 2020
  12. Dec 21, 2020
  13. Dec 18, 2020
  14. Dec 17, 2020
  15. Dec 16, 2020
  16. Dec 15, 2020
  17. Dec 14, 2020
Loading