assert(false) in release == splinter in eye
Andrei Alexandrescu
SeeWebsiteForEmail at erdani.org
Tue Oct 12 13:40:32 PDT 2010
On 10/12/10 13:58 CDT, Christopher Bergqvist wrote:
> On Tue, Oct 12, 2010 at 2:37 AM, Andrei Alexandrescu
> <SeeWebsiteForEmail at erdani.org
> <mailto:SeeWebsiteForEmail at erdani.org>> wrote:
>
> assert(false) could be in an ideal world replaced by an intrinsic
> called e.g. halt() that looks and feels like a regular function but
> is recognized by the compiler. No new keyword would be needed. But I
> don't think that would mark a significant improvement in the language.
>
>
> Would it be possible to change the compiler to only treat
> "assert(false);" specially, avoiding treating "enum a = 0; assert(a);"
> or more complex constructs that way?
Question is when to stop. assert(0), assert(false), assert(1 == 0)...
Andrei
More information about the Digitalmars-d
mailing list