19
Efficient C++: The hidden compile-time cost of auto return types
(andreasfertig.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Sep 2025
19 points (100.0% liked)
C++
2101 readers
1 users here now
The center for all discussion and news regarding C++.
Rules
- Respect instance rules.
- Don't be a jerk.
- Please keep all posts related to C++.
founded 2 years ago
MODERATORS
If a function body is expensive to parse, isn't it then a complex function body that shouldn't go into the header anyways?
If it's templated / generic, which IIRC is one of the reasons to try and use auto, then it has to go in the header anyway.
technically it doesn't have to (you can always create a .tpp (which is still technically a header, i know, but it isn't a header header)), but i get what you mean
I mean it has to functionally be a header. Could even be a
.cfile, filename extensions stopped mattering before we even had C++03 and that's saying something!