Path: eternal-september.org!news.eternal-september.org!raubtier-asyl.eternal-september.org!.POSTED!not-for-mail From: Bonita Montero Newsgroups: comp.lang.c Subject: Re: constexpr keyword is unnecessary Date: Sun, 13 Oct 2024 14:58:24 +0200 Organization: A noiseless patient Spider Lines: 27 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sun, 13 Oct 2024 14:58:03 +0200 (CEST) Injection-Info: raubtier-asyl.eternal-september.org; posting-host="c70044d56ce67ca2d81b0f66bfd60be6"; logging-data="734816"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18BhHNpuYKgvEkccgVgNdBcck3iVjftcTU=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:+tBVJWZgb1UdGNyZ0r6dP9L3Cfk= Content-Language: de-DE In-Reply-To: Am 13.10.2024 um 14:38 schrieb Thiago Adams: > Em 10/13/2024 8:49 AM, Bonita Montero escreveu: >> Am 13.10.2024 um 13:37 schrieb Thiago Adams: >> >>> Yes. >>> constexpr is like - "require the initializer to be a constant >>> expression." But the compiler will have to check it anyway. >> >> I cannot understand why you are so militantly against this >> new language feature that can be understood in 10 seconds. >> > > I have seen code like this: > > void func() > { >    constexpr int c = 1; >    f(c); > } > > For some reason, people believe that adding constexpr will magically > improve optimization. In reality, it doesn't change anything compared to > const and often reflects a misunderstanding of how the compiler works. > As a result, I end up having to explain it. In this sense, constexpr is > viral and spreads confusion. constexpr doesn't hurt.