https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79632
--- Comment #2 from Roland Illig <roland.illig at gmx dot de> --- (In reply to Eric Gallager from comment #1) > What exactly is the harm of the redundancy? I don't think this is too big of > an issue... The harm of redundancy is that there is no single point of truth. When there are two places in the code saying the same thing, it's one too much. And if they differ by a tiny bit, you cannot be sure which one is correct. The two places should always say the very same, or it gets confusing. Having redundant code is like saying what can be said in a single sentence, just that it takes more than five sentences. When the code says the same several times, it takes more time reading the code since you have to read the same sentence more than once. When the comment differs from the code, how can you say which one is the correct one? The harm of redundancy is that it costs more time to read the same sentence several times. The harm of redundancy is that it takes more time to read the same sentence twice or even more often. I hope I have made my point. :)
