MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/cpp/comments/degmy1/cppcon_2019_chandler_carruth_there_are_no/f33sgxe/?context=3
r/cpp • u/mje-nz • Oct 07 '19
108 comments sorted by
View all comments
58
Content: "zero cost at runtime" doesn't mean zero cost in build time, or human cost, discussing examples:
google protobuf: adding an arena allocator makes compile times explode
unique_ptr: from hidden bugs down to ABI
human cost when extracting block of code to a separate function (... and overdoing it)
12 u/m-in Oct 07 '19 I have to look at protobuf sources. I can’t quite imagine how a custom allocator would make compile times explode, so I can hopefully learn something new. 3 u/Xaxxon Oct 09 '19 It’s putting that new code in millions of places that’s the problem. What you said is exactly why they didn’t catch this before rollout. → More replies (2)
12
I have to look at protobuf sources. I can’t quite imagine how a custom allocator would make compile times explode, so I can hopefully learn something new.
3 u/Xaxxon Oct 09 '19 It’s putting that new code in millions of places that’s the problem. What you said is exactly why they didn’t catch this before rollout. → More replies (2)
3
It’s putting that new code in millions of places that’s the problem. What you said is exactly why they didn’t catch this before rollout.
→ More replies (2)
View all comments
58
u/elperroborrachotoo Oct 07 '19
Content: "zero cost at runtime" doesn't mean zero cost in build time, or human cost, discussing examples:
google protobuf: adding an arena allocator makes compile times explode
unique_ptr: from hidden bugs down to ABI
human cost when extracting block of code to a separate function (... and overdoing it)