Hello,
I’d like to propose a small but meaningful change to C++: making auto optional in trailing return types.
Currently, auto is required in functions that use trailing return types:
However, this requirement is redundant and misleading because:
int), so auto adds no value.auto implies type deduction, but no deduction is happening here.A more natural syntax would allow:
Not only does this improve readability and consistency with standard function declarations, but it also aligns well with Software Engineering Structural Diagrams, such as UML Class Diagrams and Object Diagrams.
In UML Class Diagrams, method return types are typically represented after the function name, similar to how trailing return types work in C++. Allowing func() -> int; without auto makes the C++ syntax closer to UML representations, enhancing clarity and traceability between a codebase and its corresponding UML models.
This proposal is backward-compatible because:
auto is already optional in normal return types:
This change is purely syntactic—it does not affect semantics.
Existing code using auto remains fully valid.
auto func() -> int; // Remains valid
auto func() -> decltype(some_expression); // Also valid
Thus, this proposal only removes an unnecessary restriction without introducing breaking changes.
Modify the C++ grammar so that functions using trailing return types no longer require auto.
This would allow:
This makes the syntax more consistent with regular function declarations.
Would this be a reasonable proposal for a future C++ standard update?
I’d love to hear your thoughts and suggestions on how this could be refined further.
Best regards,
Fady al Dhaim