Timeline for C++ "Zero Overhead Principle" in practice

Current License: CC BY-SA 4.0

8 events

when toggle format	what		by	license	comment
Jan 10, 2021 at 23:57	audit	First posts
Jan 10, 2021 at 23:58
Dec 20, 2020 at 10:53	comment	added	Doc Brown		@gnasher729: what makes you think the OP knew already, for example, what James McLeod suggested?
Dec 20, 2020 at 10:36	comment	added	gnasher729		@Doc The whole point of the question was “I think I should be able to figure out how to do this with zero overhead, but I can’t”. So now the question is reduced to “how can I do this with low overhead”, which OP knew how to do.
Dec 20, 2020 at 9:12	comment	added	user3840170		Also, the talk I linked points out how exceptions are actually in violation of the zero-overhead principle, both parts of it.
Dec 19, 2020 at 21:06	comment	added	user3840170		The zero-overhead principle is two-pronged: the first part is ‘you don’t pay for what you don’t use’ as you say, but the other is ‘if you do use it, you couldn’t have done it better by hand’ (this is how Herb Sutter uses the term for example, so it’s not just my personal opinion). The asker is clearly referring to the second part.
Dec 19, 2020 at 15:52	comment	added	davidbak		You're right about zero overhead meaning features don't cost if you don't use them. And its a darn good thing too! Because otherwise, if features also didn't cost if you did use them how would I ever get paid well for writing good clean efficient software! All C++ programs would run in zero time no matter how badly written!
Dec 19, 2020 at 13:39	comment	added	Doc Brown		Ok, the OP made the error of giving their question a misleading title. But when we put this aside for a moment, I don't see how this this answers the actual question (which is how to avoid an overly complicated approach for the described problem)?
Dec 19, 2020 at 11:52	history	answered	gnasher729	CC BY-SA 4.0