Re: [RFC][Draft] Body-less __construct
| From: | Sara Golemon | Date: | Mon, 10 May 2021 17:27:51 +0000 |
| Subject: | Re: [RFC][Draft] Body-less __construct | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-114347@lists.php.net to get a copy of this message | ||
On Mon, May 10, 2021 at 3:56 AM Marco Pivetta <ocramius@gmail.com> wrote:
> > Another point to be made here, as far as my interpretation of PSR-12, the
> > curly braces occupy two lines for methods with multiline arguments. So
> for
> > whoever follows PSR-12, it's more like this, with brackets just dangling
> > there across 2 lines.
> >
>
> Given that:
>
> *
{} can already represent what you want
> * the issue is more of a coding-style related topic
>
> I suggest bringing this up in a new PSR instead. Consider that PSR-1, PSR-2
> and PSR-12 were designed pre-PHP-8, so they will need adjustments again,
> but AFAIK nothing has moved yet, since the ecosystem is still adapting to
> the PHP 8 changes (I myself haven't finished adopting it on many of my
> libraries).
>
>
A whole lot of agreeing with Marco here. The problem is the coding
standard, not the syntax.
Also, as Guilliam said in a later reply, using semicolon already has a
meaning and this contradicts that. Let's not make the syntax more
confusing purely to avoid updating a PSR that was meant to be a living
standard.
-Sara