Traversing the Dilemma: Exploring the Trailing Return Type Syntax in C 11
C 11 introduced a novel syntax for functions, allowing developers to specify the return type after the parameter list:
auto func_name(int x, int y) -> int;
This syntax departs from the traditional declaration:
int func_name(int x, int y);
While the adoption of this new style remains limited, it prompts the question: should it become the default for new C 11 programs?
Necessity and Advantages of Trailing Return Types
In certain scenarios, trailing return types become mandatory. This includes lambda functions and decltype instances where argument names are essential.
Additionally, trailing return types offer benefits:
Mixed Style Considerations
A codebase with a mixture of traditional and trailing return types presents aesthetic concerns. However, it's worth noting that trailing return types are not universally applicable:
Conclusion
The decision whether to adopt trailing return types as the default hinges on a balance of factors. While they provide advantages in legibility and convenience, they may not be universally suitable or fully supported. For codebases requiring consistent function alignment or where member typedefs are prominent, trailing return types offer advantages. However, in situations where visibility, discoverability, or compatibility is critical, the traditional syntax may remain preferable.
The above is the detailed content of Trailing Return Types in C 11: Should They Be the New Standard?. For more information, please follow other related articles on the PHP Chinese website!