<![CDATA[MISRA Discussion Forums - 4.8 Expressions]]> https://forum.misra.org.uk/ Thu, 12 Nov 2026 23:21:40 +0000 MyBB <![CDATA[Rule 8.2.8 - why aren't aliases allowed?]]> https://forum.misra.org.uk/showthread.php?tid=1732 Tue, 18 Mar 2025 13:19:15 +0000 cgpzs]]> https://forum.misra.org.uk/showthread.php?tid=1732
Code:
    using hashPtr_t = std::uintptr_t;
    auto p2 = reinterpret_cast< hashPtr_t >( s );  // Non-compliant

However, there's nowhere in the Rule Text, Rationale or Amplification that explains why aliases are not allowed. Can you clarify?

Aliases are good for removing code duplication and ensuring the correct type is used in all contexts where it's needed; having to remove the alias and spell std::uintptr_t everywhere hurts code readability and maintainability, without any clear benefit.

Static analyzers can easily detect the usage of std::uintptr_t even if it's behind an alias.]]>
Code:
    using hashPtr_t = std::uintptr_t;
    auto p2 = reinterpret_cast< hashPtr_t >( s );  // Non-compliant

However, there's nowhere in the Rule Text, Rationale or Amplification that explains why aliases are not allowed. Can you clarify?

Aliases are good for removing code duplication and ensuring the correct type is used in all contexts where it's needed; having to remove the alias and spell std::uintptr_t everywhere hurts code readability and maintainability, without any clear benefit.

Static analyzers can easily detect the usage of std::uintptr_t even if it's behind an alias.]]>