File: itkCopy.h

package info (click to toggle)
insighttoolkit5 5.4.3-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 704,384 kB
  • sloc: cpp: 783,592; ansic: 628,724; xml: 44,704; fortran: 34,250; python: 22,874; sh: 4,078; pascal: 2,636; lisp: 2,158; makefile: 464; yacc: 328; asm: 205; perl: 203; lex: 146; tcl: 132; javascript: 98; csh: 81
file content (59 lines) | stat: -rw-r--r-- 2,558 bytes parent folder | download
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
/*=========================================================================
 *
 *  Copyright NumFOCUS
 *
 *  Licensed under the Apache License, Version 2.0 (the "License");
 *  you may not use this file except in compliance with the License.
 *  You may obtain a copy of the License at
 *
 *         https://www.apache.org/licenses/LICENSE-2.0.txt
 *
 *  Unless required by applicable law or agreed to in writing, software
 *  distributed under the License is distributed on an "AS IS" BASIS,
 *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 *  See the License for the specific language governing permissions and
 *  limitations under the License.
 *
 *=========================================================================*/

#ifndef itkCopy_h
#define itkCopy_h

namespace itk
{

/** Returns a copy of its argument. Primarily used to make the act of copying (typically involving a copy-constructor
 * call) explicit, and to avoid warnings like:
 *
 * - Microsoft Visual Studio 2022, IntelliSense Code Linter [lnt-accidental-copy] "`auto` doesn't deduce references. A
 * possibly unintended copy is being made" (https://learn.microsoft.com/en-us/cpp/ide/lnt-accidental-copy)
 * - Microsoft Visual Studio 2022, Warning C26820, "This is a potentially expensive copy operation. Consider using a
 * reference unless a copy is required (p.9)" (https://learn.microsoft.com/en-us/cpp/code-quality/c26820?view=msvc-170)
 * - Synopsys Coverity 2023.6.2, "CID 331225:  Performance inefficiencies  (AUTO_CAUSES_COPY)", "Using the `auto`
 * keyword without an `&` causes the copy of an object...".
 * - SonarSource static code analysis, "Unnecessary expensive copy should be avoided when using `auto` as a placeholder
 * type", "Avoid this unnecessary copy by using a "const" reference. (cpp:S6032)",
 * https://rules.sonarsource.com/cpp/RSPEC-6032/
 *
 * Example:
   \code
     const auto possiblyUnintendedCopy = image->GetRequestedRegion(); // Warning!
     const auto intendedCopy = Copy(image->GetRequestedRegion());     // OK, no warning  :-)
     const auto [index, size] = Copy(image->GetRequestedRegion());    // OK, no warning  :-)
   \endcode
 *
 * \note In general, it is up to the programmer to choose between doing a copy and using a reference, of course. `Copy`
 should only be used when doing a copy is preferred over using a reference.
 */
template <typename T>
[[nodiscard]] constexpr T
Copy(const T & original)
{
  // May call the copy-constructor of `T`.
  return original;
}

} // namespace itk


#endif // itkCopy_h