Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111125
MIME-Version: 1.0
References: <CAFMT4Nrnn3tvPd9jZCBg3okEuo7YKjqwXUy-vKW4WFLbpqwm4A@mail.gmail.com>
In-Reply-To: <CAFMT4Nrnn3tvPd9jZCBg3okEuo7YKjqwXUy-vKW4WFLbpqwm4A@mail.gmail.com>
Date: Wed, 22 Jul 2020 17:05:16 +0200
Message-ID: <CAP=4hCJ-Ak691TY34+mqbN-+YcSGPgo0pzMjHMvWZGY_=sUVmw@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000041c68505ab0912ec"
Subject: Re: [PHP-DEV] Changing default assertion mode to throw exceptions
From: carusogabriel34@gmail.com (Gabriel Caruso)

--00000000000041c68505ab0912ec
Content-Type: text/plain; charset="UTF-8"

On Mon, 13 Jul 2020 at 19:37, Levi Morrison <levim@php.net> wrote:

> Hello everyone,
>
> I'd like to change the default mode of assertion failures to throw.
> The current default is to warn. In my opinion this is a bad strategy:
> the engine asserted that something that is expected to be true is not,
> so executing further is a bad idea. This leaves throwing or bailing
> out. I think throwing an exception is better than bailing out, so
> that's what I propose.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php


Hello Levi

+1 on this one, I use assertions on my local development, and we also have
that
on `doctrine/coding-standard` (
https://github.com/doctrine/coding-standard/pull/47).

I think throwing an exception is indeed a better way to make the most out
of it.

--00000000000041c68505ab0912ec--