diff options
| author | MarcoFalke <[email protected]> | 2018-02-07 16:15:16 -0500 |
|---|---|---|
| committer | MarcoFalke <[email protected]> | 2018-02-07 16:15:28 -0500 |
| commit | 0277173b1defb63216d40a8d8805ae6d5d563c26 (patch) | |
| tree | c5e92d61ab80f40c7b31c36976c5ccb729198a8f /src/script/script.cpp | |
| parent | Merge #12050: [trivial] Implements a virtual destructor on the BaseRequestHan... (diff) | |
| parent | Use static_cast instead of C-style casts for non-fundamental types (diff) | |
| download | discoin-0277173b1defb63216d40a8d8805ae6d5d563c26.tar.xz discoin-0277173b1defb63216d40a8d8805ae6d5d563c26.zip | |
Merge #10498: Use static_cast instead of C-style casts for non-fundamental types
9ad6746ccd Use static_cast instead of C-style casts for non-fundamental types (practicalswift)
Pull request description:
A C-style cast is equivalent to try casting in the following order:
1. `const_cast(...)`
2. `static_cast(...)`
3. `const_cast(static_cast(...))`
4. `reinterpret_cast(...)`
5. `const_cast(reinterpret_cast(...))`
By using `static_cast<T>(...)` explicitly we avoid the possibility of an unintentional and dangerous `reinterpret_cast`. Furthermore `static_cast<T>(...)` allows for easier grepping of casts.
For a more thorough discussion, see ["ES.49: If you must use a cast, use a named cast"](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#es49-if-you-must-use-a-cast-use-a-named-cast) in the C++ Core Guidelines (Stroustrup & Sutter).
Tree-SHA512: bd6349b7ea157da93a47b8cf238932af5dff84731374ccfd69b9f732fabdad1f9b1cdfca67497040f14eaa85346391404f4c0495e22c467f26ca883cd2de4d3c
Diffstat (limited to 'src/script/script.cpp')
0 files changed, 0 insertions, 0 deletions