rspec/rules/S3646/cfamily/rule.adoc

== Why is this an issue?

It is possible in the same statement, to declare a user-defined type (``++class++``, ``++struct++``, ``++union++`` or ``++enum++``) followed by variable declarations of this type. But mixing more than one concern in a single statement is confusing for maintainers.


This rule raises an issue when a variable is declared at the end of a user-defined type declaration statement.


=== Noncompliant code example

[source,cpp]
----
struct Container { int size; } container; // Noncompliant
----


=== Compliant solution

[source,cpp]
----
struct Container { int size; };
Container container;
----


== Resources

* https://github.com/isocpp/CppCoreGuidelines/blob/036324/CppCoreGuidelines.md#Rc-standalone[{cpp} Core Guidelines C.7] - Don't define a class or enum and declare a variable of its type in the same statement



ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::message.adoc[]

include::highlighting.adoc[]

'''
== Comments And Links
(visible only on this page)

include::comments-and-links.adoc[]
endif::env-github,rspecator-view[]