Uploaded image for project: 'SonarCFamily'
  1. SonarCFamily
  2. CPP-2961

Rule S6200: Detect 'volatile' used in structured bindings, return types and function parameters

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.17
    • Fix Version/s: 6.27
    • Component/s: C, C++, Rules
    • Labels:
      None

      Description

      Even if the deprecation is only in C++20, we should report that in C++17 already...
      I don't think the RSPEC needs to be updated for this change.

      After more discussion:

      • Remove volatile parameters from rule RSPEC-3687
      • Create a new rule about declaring volatile objects for which it does not really make sense

        Attachments

          Issue Links

          depends upon

          New Feature - A new feature of the product, which has yet to be developed. CPP-2997 Clang: Warnings about deprecation of volatile in C++20 should report in all standards

          • Major - Major loss of function.
          • Closed
          implements

          Bug Detection - RSPEC-6200 "volatile" should not be used to qualify objects for which the meaning is not defined

          • Active
          is related to

          New Feature - A new feature of the product, which has yet to be developed. CPP-2914 Rule S6191: "volatile" types should not be used in compound operations

          • Major - Major loss of function.
          • Closed
          relates to

          Code Smell Detection - RSPEC-3687 Atomic types should be used instead of "volatile" types

          • Active

            Activity

              People

              Assignee:
              tomasz.kaminski Tomasz Kamiński
              Reporter:
              loic.joly Loïc Joly
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: