Hello internals, This new RFC which I'm proposing is to extend the capability of the error control operator @ to not just suppress diagnostic messages but also exceptions. It can currently be found on GitHub: [1] https://github.com/Girgias/error-control-operator-exceptions-rfc
The main motivation for this is to provide a path to migrate in a backwards compatible manner away from diagnostics such as E_WARNING to the use of exceptions without breaking 99% of PHP code which has been written in the last 25years. This proposal on it's own would not be sufficient to trigger such a change for extensions but in combination with another proposal to introduce a `throw_on_error` declare [2] it could provide a bridge for a gradual transition to the use of more exceptions internally. Although I'm not thrilled with the idea of shoving more functionality into @ I don't see any other way, and thus I think it a necessary evil to improve the long term health of the PHP project. Feedback on this RFC and different ideas on how to tackle this topic are highly appreciated and welcomed. Best regards, George P. Banyard [1] https://github.com/Girgias/error-control-operator-exceptions-rfc [2] Draft RFC for throw_on_error declare https://github.com/Girgias/php-rfc-throw-on-error-declare
