AutosarC++18_03-A13.1.2

User defined suffixes of the user defined literal operators shall start with underscore followed by one or more letters

Required inputs: IR

Possible Messages

Key	Text	Severity	Disabled
leading_space	User-defined literal operator name preceded by space.	None	False
user_defined_literal_naming	User-defined literals shall be named appropriately.	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

allow_unicode_identifiers

allow_unicode_identifiers : bool = False

Whether to allow unicode identifiers of the form (XID_start XID_continue*).

 

check_for_leading_space

check_for_leading_space : bool = False

Whether to check for and report a leading space in the operator name.

 

suffix_pattern

suffix_pattern : typing.Pattern[str] = '^_[^\W\d]+$'

Regular expression the user-defined literal suffix must match. The suffix is the part of the operator name following operator "" (e.g., _km in operator "" _km).