Project 'eclipse/simopenpass/scenario_api' was moved to 'eclipse/openpass/mantle-api'. Please update any links and bookmarks that may still have the old path.
Initial provision of a proposal for a Clang-Tidy configuration file.
3 unresolved threads
The concrete values and checks can be discussed in the course of further development.
The program was tested solely for our own use cases, which might differ from yours.
Jupp Tscheak jupp.tscheak@daimler.com, Mercedes-Benz AG on behalf of Daimler TSS GmbH
https://github.com/Daimler/daimler-foss/blob/master/PROVIDER_INFORMATION.md
Merge request reports
Activity
Filter activity
.clang-tidy 0 → 10064454 - key: readability-identifier-naming.PrivateMemberSuffix 55 value: _ 56 - key: readability-identifier-naming.ProtectedMemberSuffix 57 value: _ 58 - key: readability-identifier-naming.StaticConstantCase 59 value: CamelCase 60 - key: readability-identifier-naming.StaticConstantPrefix 61 value: k 62 - key: readability-identifier-naming.StructCase 63 value: CamelCase 64 - key: readability-identifier-naming.TemplateParameterCase 65 value: CamelCase 66 - key: readability-identifier-naming.VariableCase 67 value: lower_case 68 - key: readability-magic-numbers.IgnoredFloatingPointValues 69 value: 1e-3;1e-6; - .clang-tidy 0 → 100644
55 value: _ 56 - key: readability-identifier-naming.ProtectedMemberSuffix 57 value: _ 58 - key: readability-identifier-naming.StaticConstantCase 59 value: CamelCase 60 - key: readability-identifier-naming.StaticConstantPrefix 61 value: k 62 - key: readability-identifier-naming.StructCase 63 value: CamelCase 64 - key: readability-identifier-naming.TemplateParameterCase 65 value: CamelCase 66 - key: readability-identifier-naming.VariableCase 67 value: lower_case 68 - key: readability-magic-numbers.IgnoredFloatingPointValues 69 value: 1e-3;1e-6; 70 - key: cppcoreguidelines-avoid-magic-numbers.IgnoredFloatingPointValues - .clang-tidy 0 → 100644
32 - key: readability-identifier-naming.ClassCase 33 value: CamelCase 34 - key: readability-identifier-naming.ConstexprVariableCase 35 value: CamelCase 36 - key: readability-identifier-naming.ConstexprVariablePrefix 37 value: k 38 - key: readability-identifier-naming.EnumConstantCase 39 value: CamelCase 40 - key: readability-identifier-naming.EnumConstantPrefix 41 value: k 42 - key: readability-identifier-naming.FunctionCase 43 value: CamelCase 44 - key: readability-identifier-naming.GlobalConstantCase 45 value: CamelCase 46 - key: readability-identifier-naming.GlobalConstantPrefix 47 value: k -
This will definitely make problems in
opsimulation. I once discussed with @arauschert enums values should be prefixed withk. But do we (a) really want that and (b) like to have that too for all the other global stuff?I personally vote against this.
According to Enumeration declaration, an enumerator is an explicitly named constant.
mentioned in issue #18
mentioned in merge request !78 (merged)
Please register or sign in to reply