Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121761 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 72319 invoked from network); 22 Nov 2023 18:30:32 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Nov 2023 18:30:32 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EFCEF18004B for ; Wed, 22 Nov 2023 10:30:34 -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, HTML_MESSAGE,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-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (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 ; Wed, 22 Nov 2023 10:30:34 -0800 (PST) Received: by mail-wr1-f42.google.com with SMTP id ffacd0b85a97d-332d2b6a84cso21974f8f.0 for ; Wed, 22 Nov 2023 10:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700677829; x=1701282629; darn=lists.php.net; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=c5PZOLZP7LGlJSjIcumWEFXmCGOivtJ0Gk9VSRutgtU=; b=MOuxYP0MSycruJgf81qpvMHC+/VIuFeb64dJT3d/JXOIJGK0HRkGigjpSrD5Ltl0/p tcXQdvVcBEG2oxUZOegYPp3E5gzEiZNRrdt9Nt86KvuVuE8iVqfMqdAKM55qWMwNeIjp l3ySVRmp8KktQj+bfZAtuDSFhjf1Dp+YoFpXN9rWfjENdQRu7QfqGYSYIoWrOY/1sCkQ LkCEqNy48+gWAer5ZX3/wFf9T2cs+DH5ZLX7FWiDSGLsyXjpy/j+UUQoN/TTkdNW8Hal iGDGJJFdFAxzosDua8iSKo71dRtGudrk7/Dxyv7k53aN41zpr/EgWoX8dYNDAeYJzuVQ pGvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700677829; x=1701282629; h=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=c5PZOLZP7LGlJSjIcumWEFXmCGOivtJ0Gk9VSRutgtU=; b=Pp06K+6C50KmWnfONJLCFQwPwJeVPk2X9V1rs/4U6QoWx0kaqrET2jcqUK+djht3tQ tgLI3ES5VDum2QGiD5cA/Yu2wOFioTiQRqslBqGKsTl9hI6j4G1PTEtZHSvtxE6zMKos vQw/di6Bimd+SLjsFMxOraytvHf9QbfqlBJsmCNd94taob/tJknWSf8kSLjQFDomm4+k F6gIuWMLg8fTObnBX7ILwUtl713eO06ziQiYrkMrLwBM1NyZYkzJ7fXFWrq2GoIxuWyK 1+FMMptRqgKrVc2piO754KOapmn2fudrkD0IZOdq2QtszQ7aL7Ptf7Mjb9ixRU8yqN1g FAXQ== X-Gm-Message-State: AOJu0YzPHZlZhU+OpIB4qK4/NhNdwKTLKm6IKhy7g/JLtGilW3M7JbW4 4gA+MVjkAn9ecoKT1/vdPk7VyMpW9hSVdF6tc+khE4+UHHA= X-Google-Smtp-Source: AGHT+IEFkeiqllDA9Ykq9dg7zcyQ3FAfPytCVkaTJ/YDG51utsoSmbSaVIGOf3dPHv/s15QPkUkR0gCsusIaT4K/omI= X-Received: by 2002:adf:d1c7:0:b0:32f:83e4:50e5 with SMTP id b7-20020adfd1c7000000b0032f83e450e5mr2522196wrd.6.1700677828722; Wed, 22 Nov 2023 10:30:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 22 Nov 2023 19:30:17 +0100 Message-ID: To: PHP Internals List Content-Type: multipart/alternative; boundary="000000000000dbc455060ac1e90a" Subject: Re: [RFC] Pass Scope to Magic Accessors From: nicolas.grekas+php@gmail.com (Nicolas Grekas) --000000000000dbc455060ac1e90a Content-Type: text/plain; charset="UTF-8" Hi all, Ilija and I would like to start a discussion about the following RFC: > https://wiki.php.net/rfc/pass_scope_to_magic_accessors > > When using magic methods to access actual properties, respecting their > declared visibility is often desired. Yet, accessing the calling scope to > emulate the visibility restrictions is unreasonably difficult at the > moment. This RFC proposes to pass the calling scope to magic accessors to > make it trivial to get it. > Just a quick heads up on this thread to let you know that I'm withdrawing the RFC. I'm working with Arnaud Le Blanc on a native implementation of lazy objects and I don't need fast access to the calling scope for any other use case. If anyone has, feel free to follow up, but on my side I'm going to focus on that new soon-to-be RFC for lazy objects. Stay tuned :) Even if I'm withdrawing, I'm sending a Big Thank You to Ilija for writing the prototype implementation. Also thank you to everybody who took some time to review the proposal! Cheers, Nicolas --000000000000dbc455060ac1e90a--