Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121720 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 72679 invoked from network); 20 Nov 2023 04:17:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Nov 2023 04:17:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A474B18003B for ; Sun, 19 Nov 2023 20:17:12 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_MISSING,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-oo1-f48.google.com (mail-oo1-f48.google.com [209.85.161.48]) (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 ; Sun, 19 Nov 2023 20:17:11 -0800 (PST) Received: by mail-oo1-f48.google.com with SMTP id 006d021491bc7-5842ea6f4d5so2649423eaf.2 for ; Sun, 19 Nov 2023 20:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sensational.ch; s=google; t=1700453828; x=1701058628; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qTlUuBSSmsC5X6yDgZkyGz7W5ZtTL7TTURTtA4GyUYY=; b=j1BfBuF9mpG/ZOZx4bEN73et4XqaehefO/4lh8rl9Z80fuY9nHSPAhPXtmiTQd6SfI rBCmfgfjOnUmBVZZl4PwSLb20YKhOSrkIDQGLsL+fVm7SbatykjYbrl4MR4VHUocx98y gYHPZ5GvCKMh6ZQjV2w1jwiDjkvBEwmEO0RJ6YpoaaQE2g63cLLkvfXOREuKT7Uto1ik YpZOvmOGVlDzfIhjrVKIn8CSdrMBjJ96MfHByLqGa1luqw+PUlCZkw0Xa+AcCA4UtVkG wvIXC/kR35rdAaDj63c1DYA9tb5E2KNtkftA5QYNYsKB0yJoJJE7+j6gpbZDwwXuS4ad e14A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700453828; x=1701058628; 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=qTlUuBSSmsC5X6yDgZkyGz7W5ZtTL7TTURTtA4GyUYY=; b=hQg7UGh/H9PwuugRhFzeOt9kardTI8P/ubKKYObjfV2OJQmoEtlVg3UjyJLREbmmLX xcuSYgrqVNlcFw7p9OFXELdJIN7ZJtUyf7r++JjCIjjxRv6UL6yDm89jg81gdzNRMZx3 rnaH2u7jgHH8XWxMd5eCl6GCxGaEHoUiAcDG65dU0uAo//anmHfgJ498BaiTVNxbsk6g vv82ja3qN+iXA/+NQab6SuvVmoNFzN9Bnz+g98ridOyVj3BuZDFbGUYq+rV3YqJEhUuR 4GvsFe5aOkNhNsGzjpZwQc2RteOI3bykns+1kkdn5K2/uwiaT9Q8JT4VYwnWS2L7b/wp BiXg== X-Gm-Message-State: AOJu0YzawozalzgLR8lCZ6XRI02XTw/s7IYICozcO2pnOVHqPmQLPlE7 scT2nXjF/Rk+2I7RyG/jwPgHqZBJUk/Ci91G7jJFLw== X-Google-Smtp-Source: AGHT+IGJPQr+xOyNRvlrZgh3EMkne0y7tmaeUKyf9ZpMJK7XY9QqRr89R8pgAEJsUq7dXNBflV3KTluLJLj1J1h64q0= X-Received: by 2002:a05:6820:549:b0:57b:92f2:1f64 with SMTP id n9-20020a056820054900b0057b92f21f64mr7970928ooj.8.1700453828661; Sun, 19 Nov 2023 20:17:08 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 20 Nov 2023 05:16:57 +0100 Message-ID: To: Jakub Zelenka Cc: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000006a27ab060a8dc2b9" Subject: Re: [PHP-DEV] [RFC] [Discussion] Resource to object conversion From: phofstetter@sensational.ch (Philip Hofstetter) --0000000000006a27ab060a8dc2b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Thu, Nov 16, 2023 at 17:14 Jakub Zelenka wrote: > I will personally vote against this if there is no is_resource > change as I think it's just too big BC break even for 9.0 - it will likel= y > require massive update of many code bases. As someone maintaining a large code-base going back to 5.0.0 and bitten in the past by the resource thing, I wonder whether it was previously discussed to have all these converted objects implement a `Resource` interface and have `is_resource()` check for that. Both the function and maybe also the interface could then also be marked as deprecated, but it would allow for a much more painless transition. Personally, I=E2=80=99m now relying on psalm to detect such issues, so if I= had a vote I would selfishly vote yes anyways, but still: for those without static analysis, this would IMHO make things much easier. Philip --0000000000006a27ab060a8dc2b9--