stink [none/use name]@hexbear.net to Slop.@hexbear.netEnglish · 21 days agoNotePad++ Tiny Man Mogging Coomer Editionhexbear.netimagemessage-square46linkfedilinkarrow-up198arrow-down14file-text
arrow-up194arrow-down1imageNotePad++ Tiny Man Mogging Coomer Editionhexbear.netstink [none/use name]@hexbear.net to Slop.@hexbear.netEnglish · 21 days agomessage-square46linkfedilinkfile-text
minus-squareRedNajm [any]@hexbear.netlinkfedilinkEnglisharrow-up4·20 days agohttps://godbolt.org/z/3dTbzfn68 It does, and i’d assume all production-grade C++ compilers do. I guess it’s just a technicality in the C++ specification
minus-squareImnecomrade [none/use name]@hexbear.netlinkfedilinkEnglisharrow-up3·edit-220 days agoBased on my limited research, it sounds like some optimizations may occur for built-in types, but may not occur for user-defined types. https://softwareengineering.stackexchange.com/questions/358725/pre-increment-vs-post-increment https://cplusplus.com/forum/general/102639/ https://stackoverflow.com/questions/38947790/efficiency-of-postincrement-v-s-preincrement-in-c https://stackoverflow.com/questions/24901/is-there-a-performance-difference-between-i-and-i-in-c
https://godbolt.org/z/3dTbzfn68
It does, and i’d assume all production-grade C++ compilers do. I guess it’s just a technicality in the C++ specification
Based on my limited research, it sounds like some optimizations may occur for built-in types, but may not occur for user-defined types.
https://softwareengineering.stackexchange.com/questions/358725/pre-increment-vs-post-increment
https://cplusplus.com/forum/general/102639/
https://stackoverflow.com/questions/38947790/efficiency-of-postincrement-v-s-preincrement-in-c
https://stackoverflow.com/questions/24901/is-there-a-performance-difference-between-i-and-i-in-c
Interesting, thank you!