On Fri, Jul 11, 2025, at 02:40, Nick wrote:
> Hey Rob,
>
>> On 11. Jul 2025, at 01:43, Rob Landers wrote:
>>>
>>> Nick previously suggested having the get-hook's first return value cached;
>>> it would still be subsequently called, so any side effects would still
>>> happen (though I don't kno
Hey Eric,
> On 11. Jul 2025, at 10:08, Eric Norris wrote:
>
> Regarding the caching option suggested elsewhere, the semantics
> mentioned seem confusing to me. The body is called on subsequent gets,
> but only the value from the first get is returned? I would expect that
> would be very confusin
Hey all,
> On 8. Jun 2025, at 11:16, Larry Garfield wrote:
>
> As Nick has graciously provided an implementation, we would like to open
> discussion on this very small RFC to allow `readonly` on backed properties
> even if they have a hook defined.
>
> https://wiki.php.net/rfc/readonly_hooks
Hey Tim,
> On 10. Jul 2025, at 17:37, Tim Düsterhus wrote:
>
> Hi
>
> Am 2025-07-08 17:10, schrieb Larry Garfield:
>> The only way to make the readonliness fully guaranteed would be to force a
>> readonly property to be cached
>
> Or by not allowing a `get` hook on readonly properties, of cou
On Wed, Jul 9, 2025 at 1:50 PM Larry Garfield wrote:
>
> On Wed, Jul 9, 2025, at 10:42 AM, Eric Norris wrote:
> >> An init hook would be clearer, certainly, though it also has its own edge
> >> cases. Can you set something that has an init hook? What happens if
> >> there's both a get and init
Hey Rob,
> On 11. Jul 2025, at 01:43, Rob Landers wrote:
>>
>> Nick previously suggested having the get-hook's first return value cached;
>> it would still be subsequently called, so any side effects would still
>> happen (though I don't know why you'd want side effects), but only the first
>
On Thu, Jul 10, 2025, at 17:34, Larry Garfield wrote:
> On Thu, Jul 10, 2025, at 5:43 AM, Tim Düsterhus wrote:
> > Hi
> >
> > Am 2025-07-08 17:32, schrieb Nicolas Grekas:
> >> I also read Tim's argument that new features could be stricter. If one
> >> wants to be stricter and forbid extra behavio
On Thu, Jul 10, 2025, at 5:43 AM, Tim Düsterhus wrote:
> Hi
>
> Am 2025-07-08 17:32, schrieb Nicolas Grekas:
>> I also read Tim's argument that new features could be stricter. If one
>> wants to be stricter and forbid extra behaviors that could be added by
>> either the proposed hooks or __get, the
On Wed, Jul 9, 2025, at 10:22 PM, Ben Ramsey wrote:
> Hello internals,
>
> I’m opening discussion on an RFC proposing that we relicense PHP under
> the Modified BSD License (SPDX identifier: BSD-3-Clause), starting with
> PHP 9.0. This change simplifies and modernizes our licensing,
> addressing lo
Hi
Am 2025-07-02 18:23, schrieb Arnaud Le Blanc:
We will update the RFC, but here are a few answers:
I don't think this has happened yet.
On Wednesday, July 2nd, 2025 at 17:05, Tim Düsterhus
wrote:
How will PFA calls appear in a stack trace and how will PFA Closures
look like to `var_dump(
On 10.07.2025 at 14:06, Tim Düsterhus wrote:
> Am 2025-07-09 12:34, schrieb Christoph M. Becker:
>
>> That *might* give users only a year to fix the deprecated features, what
>> might not match everybody's pace, though.
>
> Each PHP version is supported for 4 years by the PHP project [1], thus
>
Hi
Am 2025-07-09 12:34, schrieb Christoph M. Becker:
The RFC at hand states:
| The RFC proposes to deprecate the listed functionality in PHP 8.5 and
| remove it in PHP 9 (except where otherwise noted).
That *might* give users only a year to fix the deprecated features,
what
might not match e
On 10 July 2025 01:52:17 BST, Deleu wrote:
>On Wed, Jul 9, 2025 at 7:23 PM Rowan Tommins [IMSoP]
>wrote:
>
>> On 09/07/2025 17:39, Deleu wrote:
>> > It's currently undeniable that a Unit Enum name is a string.
>>
>> If you want to associate a single string value with each enum case, use
>> a stri
On Wednesday, 9 July 2025 at 22:26, Claude Pache wrote:
> Hi,
>
> A possible reason for wanting to use the non-canonical names in settype(), is
> that those names are returned by gettype(). Fictional example (not intended
> to be reasonable, only illustrative):
>
> ```php
> function settype_fro
On Thursday, 10 July 2025 at 04:25, Ben Ramsey wrote:
> Hello internals,
>
> I’m opening discussion on an RFC proposing that we relicense PHP under
> the Modified BSD License (SPDX identifier: BSD-3-Clause), starting with
> PHP 9.0.
Hello Ben,
Thank you for tackling this thorny issue, I sincere
Hi
Am 2025-07-08 17:32, schrieb Nicolas Grekas:
I also read Tim's argument that new features could be stricter. If one
wants to be stricter and forbid extra behaviors that could be added by
either the proposed hooks or __get, then the answer is : make the class
final. This is the only real way t
Hi
Am 2025-07-08 17:10, schrieb Larry Garfield:
The only way to make the readonliness fully guaranteed would be to
force a readonly property to be cached
Or by not allowing a `get` hook on readonly properties, of course.
Best regards
Tim Düsterhus
On 10 July 2025 06:28:39 CEST, Daniel Scherzer
wrote:
>* https://wiki.php.net/rfc/datetime_and_daylight_saving_time was accepted
>in 2011
>
>Is anyone still working on these?
Sort of, as part of new date time work.
cheers
Derick
18 matches
Mail list logo
