File: misplaced-const.rst

package info (click to toggle)
llvm-toolchain-16 1%3A16.0.6-15~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,634,792 kB
  • sloc: cpp: 6,179,261; ansic: 1,216,205; asm: 741,319; python: 196,614; objc: 75,325; f90: 49,640; lisp: 32,396; pascal: 12,286; sh: 9,394; perl: 7,442; ml: 5,494; awk: 3,523; makefile: 2,723; javascript: 1,206; xml: 886; fortran: 581; cs: 573
file content (25 lines) | stat: -rw-r--r-- 931 bytes parent folder | download | duplicates (28)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
.. title:: clang-tidy - misc-misplaced-const

misc-misplaced-const
====================

This check diagnoses when a ``const`` qualifier is applied to a ``typedef``/
``using`` to a pointer type rather than to the pointee, because such constructs
are often misleading to developers because the ``const`` applies to the pointer
rather than the pointee.

For instance, in the following code, the resulting type is ``int * const``
rather than ``const int *``:

.. code-block:: c++

  typedef int *int_ptr;
  void f(const int_ptr ptr) {
    *ptr = 0; // potentially quite unexpectedly the int can be modified here
    ptr = 0; // does not compile
  }

The check does not diagnose when the underlying ``typedef``/``using`` type is a
pointer to a ``const`` type or a function pointer type. This is because the
``const`` qualifier is less likely to be mistaken because it would be redundant
(or disallowed) on the underlying pointee type.