andreasfertig@programming.dev to C++@programming.dev · 6 months agoEfficient C++: The hidden compile-time cost of auto return typesandreasfertig.comexternal-linkmessage-square9fedilinkarrow-up117arrow-down10
arrow-up117arrow-down1external-linkEfficient C++: The hidden compile-time cost of auto return typesandreasfertig.comandreasfertig@programming.dev to C++@programming.dev · 6 months agomessage-square9fedilink
minus-squareDapperPenguin@programming.devlinkfedilinkarrow-up3·6 months agoFrom my discussion with C++ folk, auto is just part of the “modern” way of doing c++. Paired with the -> return type. Perhaps including that -> return type negates this problem? It’s still strange to me. Feels more like Rust
minus-squarebitcrafter@programming.devlinkfedilinkarrow-up2·6 months agoOne day the use of auto will grow so extensive that modern Python code will have more type annotations than modern C++ code!
From my discussion with C++ folk, auto is just part of the “modern” way of doing c++. Paired with the -> return type. Perhaps including that -> return type negates this problem? It’s still strange to me. Feels more like Rust
One day the use of
autowill grow so extensive that modern Python code will have more type annotations than modern C++ code!