Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120336 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71644 invoked from network); 18 May 2023 08:12:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 May 2023 08:12:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0B69C1804D7 for ; Thu, 18 May 2023 01:12:41 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-pg1-f171.google.com (mail-pg1-f171.google.com [209.85.215.171]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 18 May 2023 01:12:40 -0700 (PDT) Received: by mail-pg1-f171.google.com with SMTP id 41be03b00d2f7-5346d150972so410442a12.3 for ; Thu, 18 May 2023 01:12:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684397559; x=1686989559; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pAEisXbgEcePE+2Vf7STelSOEM77DFtpKTD0jHoboQg=; b=sBcH1LjofNoSgc/9mZLSEjvAlnQLXUiZF5+Hfqr3YrnO0yx4C9k2IWjaOQbxwS+mOe UpFtmLwncYBL2c+ue1FV8EB4LHmapBYQU4N6P6aJ/VD8SQouTnJ1ACoRF178zWGb1nCA ytov7sikRIdNMv+gZO5XdJrukVGuCvn1wFnpQ9OPJB5AAp3RseKVgsBt1gS0sanxk8NX evPOhUNAFQCIxeisBvn3IgtM1MirpFINORDVxenjG1ORGFmhK9Vu0dFXdiSLiSgNLzRY KXHnd/b2K6Gr9/MhHfIPw40nvo9pPOdt1iJjtTULgXgtQfTtQJqA2P37E2Dgx1KsBVKG eraQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684397559; x=1686989559; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pAEisXbgEcePE+2Vf7STelSOEM77DFtpKTD0jHoboQg=; b=HAob01cpRuScMOMHVHnoAz2dpN5d8XYMEAFQS9i0nW6Gi3LijwnIxeNE4y3IUl4Gip j1ec5Eu2Rs22bFamvJ2xlYyoPqCbOAeWWUHBbgNCyDLvU2COoDQRVx62GnbQoFFyHZ5N HBGk3ioi/i7451breM3Loh3fJUVOOTrU60JGF4emH7dAYxLdLIYi3LNicTpoFOnVRzcK GQnv1x3NMj33nRI9LHeuJUADy8H7nTm1AF0kKgZbj8IdXrr24hOZ7qA4Ydqj+g8Nh22I xY3k5lbZeT07KXfefx1Xu3q8j/Eeylj/1Dx0t/ZylKFdG47Db0Q73vl/Opo1ubGcjnrt ob/A== X-Gm-Message-State: AC+VfDzO3HVoZjUg3Y50nu/Zsoxbo46xH6zakL5AQhNc7d2bSOejRsJI A1fMg7ugXfu7wZ3WEFXi1b9ZxlFe9+Isc3SH3y9oehHm9TA= X-Google-Smtp-Source: ACHHUZ55lVbCyL9w9DPK8vO2oDREacPwXJS5P6oFeKyUXzVfT22qHiY8fv8AELEYtyfzSFl0vGtLyuvb/E71iTzFjhg= X-Received: by 2002:a17:90a:764d:b0:253:30f9:1849 with SMTP id s13-20020a17090a764d00b0025330f91849mr1753936pjl.12.1684397559228; Thu, 18 May 2023 01:12:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 18 May 2023 10:12:28 +0200 Message-ID: To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000002db1c405fbf35e79" Subject: Re: [PHP-DEV] RFC [Discussion]: Marking overridden methods (#[\Override]) From: ocramius@gmail.com (Marco Pivetta) --0000000000002db1c405fbf35e79 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Tim, On Thu, 11 May 2023, 18:37 Tim D=C3=BCsterhus, wrote: > Hi > > I'm now opening discussion for the RFC "Marking overridden methods > (#[\Override])": > > ---- > > RFC: Marking overridden methods (#[\Override]) > https://wiki.php.net/rfc/marking_overriden_methods > > Proof of concept implementation is in: > > https://github.com/php/php-src/pull/9836 The idea is neat, but the trend is roughly: * Many moving to `final` classes (finally!) * Moving to less methods in an `interface` (some RFCs around functional interfaces, even) I am not sure this RFC is really relevant: I can see some use in generated code, since this would act as an engine-level checksum for some minimal changes, but otherwise it's a bit bloated? Would it perhaps make sense to have this in userland first, in phpstan or psalm plugins, to see if there is interest? --0000000000002db1c405fbf35e79--