Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118121
MIME-Version: 1.0
References: <982FFD13-6B2C-4A28-8091-886F2F637B86@me.com>
In-Reply-To: <982FFD13-6B2C-4A28-8091-886F2F637B86@me.com>
Date: Wed, 29 Jun 2022 17:42:46 +0200
Message-ID: <CAC5V6giM3+WZ2SR-wZbqoH_quypc1ojXNiKWSCucnM30S_TNDg@mail.gmail.com>
To: Antoine MAKDESSI <amakdessi@me.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Exception type hint
From: guilliam.xavier@gmail.com (Guilliam Xavier)

Hi (note: your message was flagged as spam),

> https://github.com/php/php-src/issues/8843

So I understand it as having a "true code" equivalent for the
`@throws` phpDoc comment (similar to type declarations for `@param`
and `@return`)? which would also be checked at run-time?

Just my 2 cents on that (let's call it "exception specification"):

  1. IMHO, it shouldn't be mixed in the return type declaration (with
a union-like syntax) but separated and independent (e.g. with a
`throws` keyword, and pipes [or commas] between multiple exception
classes)
  2. AFAIK, Java has it (mandatory to compile for "checked
exceptions", sometimes controversial), C++ used to have it
(runtime-checked) but dropped it (and introduced `noexcept` instead);
I don't know of any dynamic language that has it

You would also need to define how it plays with inheritance (and
reflection), and what exactly should happen when a function throws an
exception it didn't "declare"...

PS: I also found some old feature requests:
  - https://externals.io/message/4424
  - https://bugs.php.net/bug.php?id=42251
  - https://bugs.php.net/bug.php?id=62404
  - https://bugs.php.net/bug.php?id=67312

Regards,

-- 
Guilliam Xavier