Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121730 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 20924 invoked from network); 20 Nov 2023 16:43:37 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Nov 2023 16:43:37 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3E90D18002B for ; Mon, 20 Nov 2023 08:43:39 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com [209.85.128.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 20 Nov 2023 08:43:38 -0800 (PST) Received: by mail-wm1-f54.google.com with SMTP id 5b1f17b1804b1-40b23aeb9d9so8026495e9.3 for ; Mon, 20 Nov 2023 08:43:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700498614; x=1701103414; darn=lists.php.net; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=SkOYAO/eYzQ5jXyYn0bU/QCtcr4Mz0wng4Tk2itsY58=; b=WYqsW8OApofaEdk6iTB+epWgF723z6YVB5fpOF0Jpc27hgze8qsU5/9kg8S2AvFHJL wh5mOnk6gB7GQ+VXebw/v75D2xLxzjx5gsnao01QoDDpVtuQo4058JK1MgsPMarWlMGB WbYKS0iTv8FqzpO8mKllPMtCxF2Qap2h24YzNrIwOye7hEGbyCxPh8x4vRZv4MY25wRp wbBJXPILTOiRobmH4TxTFZLTOHC6SeyzaAi9EI7QCwYHSe29KGc6Gj61P/rCp8Wsh8oj DV7ns2FuUuZOvzbMoQjV7QzAGLrX2TAU25Ti6z+9QvENHqkl5oGZqrEvHO3wLGrBecen PfiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700498614; x=1701103414; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=SkOYAO/eYzQ5jXyYn0bU/QCtcr4Mz0wng4Tk2itsY58=; b=HGfwlDwQg+WLcZxzdH1N0IuMrQjd74JKu8BW+HeFNbc8tUGo+J1j6+yp3PC1CGi9mS mIGTEf4p8V9tB/8JQyZqcg7AOApBPdcNnjjnwJWQtndiSHk61KjYO0dIN1PoW8n6wmUY sHg6bIU2i9bPTmlPuK1hZIPDktgg1Q7aDAHQ2JLMA3gGvu3p26+1ojE1QB9AibwhvdGJ 9DPJ0a13j5mb06vggSBOmFJ+g94ba3dh8A5PwpmfCIqfn3CmiUzxtVzRI6RPWVdLNPHW 6ezaXHCdZR2XO7W/tR+CWNxCzqP4sX24fZ8W0HeD05cXJbc7pInozzl7+HNB7s7DJaf1 u8rQ== X-Gm-Message-State: AOJu0Yw+t3lruklEswovb4Ds8uOToiyNjpz8QNlz+G1Eav4ad/ZFB/0P 3FYJM7kSFO62AAnPaOpG/WfE5l/Dobg= X-Google-Smtp-Source: AGHT+IFzmLZxq2nW5U/WK3Gm3UcoasQuyAYSL4B1/93R5AZLNoDH0mi+6sWHyc2KwBznrZHQ7mguuQ== X-Received: by 2002:a05:600c:4f05:b0:408:543d:5536 with SMTP id l5-20020a05600c4f0500b00408543d5536mr6682416wmq.4.1700498614049; Mon, 20 Nov 2023 08:43:34 -0800 (PST) Received: from [127.0.0.1] (cpc83311-brig21-2-0-cust191.3-3.cable.virginm.net. [86.20.40.192]) by smtp.gmail.com with ESMTPSA id d15-20020adffd8f000000b003316debbde4sm9724480wrr.48.2023.11.20.08.43.33 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Nov 2023 08:43:33 -0800 (PST) Date: Mon, 20 Nov 2023 16:43:32 +0000 To: internals@lists.php.net User-Agent: K-9 Mail for Android In-Reply-To: References: <79d675e3-95b4-40bb-baf4-3e1c998f5390@online-presence.ca> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC Proposal - static modifier for classes From: rowan.collins@gmail.com (Rowan Tommins) On 20 November 2023 08:35:15 GMT, Lanre Waju w= rote: >1=2E I will personally implement this feature=2E That's good to hear, but the initial implementation is not the main cost o= f a new feature=2E Once we add something, it's very hard to remove, and eve= ry future change has to consider that feature and make sure it doesn't brea= k=2E That's why "do we need X when Y does nearly the same thing" is a more vali= d argument (in general) than you're giving it credit for: if we included ev= ery variation of every feature, the language and its implementation would b= ecome unmanageably complex, so we have to choose where to draw the line=2E It's up to the person proposing a feature to persuade others that it falls= the right side of that line - that the benefit of the feature outweighs th= e cost of having it in the language=2E (It's also worth noting that the previous proposal also had an implementat= ion, linked at the bottom of the RFC=2E) It's probably not productive to just say "the people who voted last time a= re wrong", but it was long enough ago that a new RFC on the topic wouldn't = break any rules=2E So, if you want to proceed with this, you can try to com= e up with a justification that addresses the points raised previously, and = follow the process here: https://wiki=2Ephp=2Enet/rfc/howto Regards, --=20 Rowan Tommins [IMSoP]