To Trail or Not to Trail: Should C 11 Functions Use Trailing Return Types?

Trailing Return Types: A Stylistic Choice for C 11 Programs

C 11 introduces the concept of trailing return types, a new syntax that allows developers to declare the return type of a function after its arguments. This has sparked a debate on whether it should become the default style for new C 11 programs.

Reasons for Using Trailing Return Types

While trailing return types may seem unfamiliar, they offer several advantages:

• Clarity: Explicitly specifying the return type in the function signature can improve readability, especially in cases where the return type is complex or ambiguous.
• Reduced Code Duplication: In member function definitions, trailing return types eliminate the need to repeat class and member type qualifications.
• Alignment: Consistent use of trailing return types results in aesthetically pleasing code, with all function names aligned vertically.

Cases Where Trailing Return Types Are Required

Certain scenarios demand the use of trailing return types:

• Lambda return types, when specified, must be defined as trailing return types.
• Declining return types that depend on argument names in the scope.

Should Trailing Return Types Be the Norm?

Whether trailing return types should be universally adopted is a matter of personal preference. Some developers favor the traditional syntax for its familiarity, while others prefer the enhanced clarity and code aesthetics provided by trailing return types.

For new C 11 projects, it is important to establish a consistent style to avoid a mix of syntax. However, the decision ultimately depends on the context, readability, and personal preferences of the project team.

The above is the detailed content of To Trail or Not to Trail: Should C 11 Functions Use Trailing Return Types?. For more information, please follow other related articles on the PHP Chinese website!