AUTOSAR C++:2014 rules
Threads
- A8-4-5: Should have an exception for move constructors (0 Replies)
- A7-2-1 Still relevant in C++14? (1 Reply)
- A18-9-4 (2 Replies)
- A8-4-5: are partial moves allowed? (1 Reply)
- A27-0-1 Unclear scope of the rule (1 Reply)
- A13-5-4 opposite operator clarification (1 Reply)
- cvalue and constant integral expression in generic context (1 Reply)
- final means "final" (7 Replies)
- A4-5-1 with overloading operator<< (2 Replies)
- A3-9-1 exception for using "unsigned char" for storage? (2 Replies)
- A12-1-1 - Does it apply to POD structs? (5 Replies)
- A7-1-2: Is it really intented to mark also functions as constexpr? (3 Replies)
- A20-8-2 / A20-8-3 - Is returning a non-owning pointer always a violation? (4 Replies)
- A3-9-1 - example with plain 'char' type (2 Replies)
- A6-4-1 What is the definition of a "case-clause"? (1 Reply)
- A8-5-2 + A8-5-3: No usage of auto allowed? (2 Replies)
- A5-2-6 about operands consisting of a sequence of only `&&` or `||` (2 Replies)
- A16-0-1 Use #define for conditional file inclusion? (3 Replies)
- A7-1-1 and function parameters (2 Replies)
- Why example in Rule A5-0-2 is non-complient (1 Reply)
- What is the intention of A15-4-4 (1 Reply)
- Rule A12-8-4 and default constructing data members in a move constructor (2 Replies)
- Conflict 12-1-3 and 12-1-2 (1 Reply)
- A4-5-1 with ternary conditional operator (1 Reply)
- A5-16-1 Clarification (2 Replies)
- Rule M7-3-4 and UDLs (3 Replies)
- A12-4-1 - Does it apply to private inheritance? (4 Replies)
- M9-3-3 and observable state (3 Replies)
- std::exception is not a catch-all (1 Reply)
- forum thread header table is wrong (1 Reply)
- A20-8-6 (1 Reply)
- A3-1-5 - Rationale and example inconsistent with rule headline? (3 Replies)
- A5-0-4 - Does the rule apply to range-based for loops? (3 Replies)
- Rule A13-2-3 - Relational operator shall return a boolean value (1 Reply)
- New forum for AUTOSAR rule questions (0 Replies)