andreasfertig@programming.dev to C++@programming.dev · 10 days agoEfficient C++: The hidden compile-time cost of auto return typesandreasfertig.comexternal-linkmessage-square13linkfedilinkarrow-up119arrow-down10
arrow-up119arrow-down1external-linkEfficient C++: The hidden compile-time cost of auto return typesandreasfertig.comandreasfertig@programming.dev to C++@programming.dev · 10 days agomessage-square13linkfedilink
minus-squareDapperPenguin@programming.devlinkfedilinkarrow-up3·9 days 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·9 days 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!