Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c++
Subject: Re: Static_assert in 2017 C++
Date: Tue, 03 Sep 2019 00:35:28 -0700
Organization: None to speak of
Lines: 15
Message-ID: <lnk1apx267.fsf@kst-u.example.com>
References: <31f1dc85-3b69-4787-8fa8-e4ee5836c609@googlegroups.com> <qkl11i$gpv$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="19288dbe6d8a7942e286fe9539db231f"; logging-data="1444"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19W1pEeJASpWCyPuSNCiJUw"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:Y1lGUk/iZTNfdh1L/ACgm1Kuaz8= sha1:wy1Z0PO5qW5brxr6UX97W7Hv//Q=
Xref: csiph.com comp.lang.c++:68155

David Brown <david.brown@hesbynett.no> writes:
[...]
> The static_assert message is what users see when the assertion fails. 
> That is your guide.

For certain values of "users".  The message is seen when the code is
compiled.  For most software, most end users use precompiled
executables.

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */