AutosarC++18_03-A0.1.6

There should be no unused type declarations

Required inputs: IR

Possible Messages

Key	Text	Severity	Disabled
unused_type	Unused type declaration	None	False

Options

• This rule shares the following common options: exclude_in_macros, exclude_messages_in_system_headers, excludes, extend_exclude_to_macro_invocations, includes, justification_checker, languages, post_processing, provider, report_at, severity

• The following places define options that affect this rule: Stylechecks, Analysis-GlobalOptions

ignore_anonymous_unions

ignore_anonymous_unions : bool = True

Unnamed types are usually ignored. But anonymous unions can be considered as violations if any members are used.

 

ignore_explicit_specializations

ignore_explicit_specializations : bool = False

Ignore violations for explicit specializations.

 

ignore_template_class_types

ignore_template_class_types : bool = True

Ignore violations for template class types as some of those are also detected for uninstantiated templates.

 

ignore_template_parameters

ignore_template_parameters : bool = False

Ignore violations for template parameters.

 

restrict_to_limited_visibility

restrict_to_limited_visibility : bool = False

Restricts violations to types with limited visibility, i.e. types declared in block scope or in unnamed namespace scope.

 

suppress_attribute_maybe_unused

suppress_attribute_maybe_unused

Type: FilterAction

Default: 'suppress'

Filter action to apply to violations for objects marked as [[maybe_unused]] or __attribute__((unused)). If set to "suppress", findings will be reported but marked as suppressed. If set to "exclude", findings will not be reported at all. If set to "normal", no special treatment is applied and the finding is reported as usual.

 

Option Types

These types are used by options listed above:

FilterAction

Used for the return value of add_filter() callbacks.

 

normal

The violation proceeds as usual.

exclude

The violation is excluded: The violation is discarded as if `--exclude` applied to it. The following filters won't get to see the violation, and it will not be imported into the database under any circumstances.

suppress

The violation is suppressed as if `AXIVION DISABLE` applied to it. Whether the violation gets imported into the database is controlled by the Axivion CI configuration.