On Sun, Jul 20, 2025 at 4:19 PM Rob Landers wrote:
>
>
>
> On Sun, Jul 20, 2025, at 19:18, Eric Norris wrote:
>
> Hi Rob,
>
> I'm going to respond to a few points from earlier emails here instead
> of each one.
>
> On Sat, Jul 19, 2025 at 6:13 AM Rob Landers wrote:
> >
> >
> >
> > On Sat, Jul 19,
Hi internals,
after two weeks of a rather uneventful discussion, I’ve opened the vote for my
RFC proposing to extend the target of the #[\Override] attribute to properties.
The vote will run for two weeks, until August 5, 00:00:00 UTC.
RFC: https://wiki.php.net/rfc/override_properties
Implement
On Fri, Jul 4, 2025 at 11:01 PM Jakub Zelenka wrote:
> Hello,
>
> I would like introduce and open discussion for RFC proposing the addition
> of JSON Schema validation support to JSON extension:
>
> https://wiki.php.net/rfc/json_schema_validation
>
> If this is successful, it should be just the f
On Sat, Jul 5, 2025 at 4:30 PM Daniel Scherzer
wrote:
> Hi internals,
>
> I'd like to start the discussion for a new RFC about adding support for
> #[\Deprecated] on traits.
>
> * RFC: https://wiki.php.net/rfc/deprecated_traits
> * Implementation: https://github.com/php/php-src/pull/19045
>
> --D
On Sat, Jul 5, 2025 at 4:23 PM Daniel Scherzer
wrote:
> Hi internals,
>
> I'd like to start the discussion for a new RFC about adding
> a FILTER_THROW_ON_FAILURE flag to the filter extension.
>
> * RFC: https://wiki.php.net/rfc/filter_throw_on_failure
> * Implementation: https://github.com/php/ph
On Mon, Jul 21, 2025 at 10:47 AM Eric Norris wrote:
>
> On Mon, Jul 7, 2025 at 12:53 PM Eric Norris wrote:
> >
> > On Wed, Jul 2, 2025 at 11:48 AM Eric Norris wrote:
> > >
> > > > Based on the feedback so far (I do plan on waiting for more responses
> > > > to your email), and on my own preferen
> On 17. Nov 2024, at 06:14, Rob Landers wrote:
>
> Hello internals,
>
> I'm ready as I'm going to be to introduce to you: "Records"
> https://wiki.php.net/rfc/records!
>
> Records allow for a lightweight syntax for defining value objects. These are
> superior to read-only classes due to hav
On Mon, Jul 21, 2025, at 13:02, Nick wrote:
>
>> On 17. Nov 2024, at 06:14, Rob Landers wrote:
>>
>> Hello internals,
>>
>> I'm ready as I'm going to be to introduce to you: "Records"
>> https://wiki.php.net/rfc/records!
>>
>> Records allow for a lightweight syntax for defining value objects.
Hey Niels,
> On 21. Jul 2025, at 15:56, Niels Dossche wrote:
>
> On 21/07/2025 10:29, Nick wrote:
>> @Niels
>> I saw you voted “no” for `set`.
>> I double checked the full RFC discussion. You didn’t participate at all
>> until the very end.
>> Both mails were on a meta-level. None one your ma
Hello internals,
I have started the vote for my "Deprecate type juggling to and from bool type
within the function type juggling context" RFC:
https://wiki.php.net/rfc/deprecate-function-bool-type-juggling
It will run for two weeks and close on Monday the 4th of August.
Best regards,
Gina P. B
On 21/07/2025 10:29, Nick wrote:
> @Niels
> I saw you voted “no” for `set`.
> I double checked the full RFC discussion. You didn’t participate at all
> until the very end.
> Both mails were on a meta-level. None one your mails had any arguments which
> would justify your vote.
> I don’t underst
On 21/07/2025 11:11, Nick wrote:
> Thanks for the detailed answer--I get it.
> I honestly would have appreciated to see you hop in with that in the earlier
> state of the RFC.
> It would have been more productive from my point of view. Maybe next time!
Hi Nick.
Honestly, it would've been extrem
Hi
Am 2025-07-21 10:29, schrieb Nick:
I saw you voted “no” for `get` (expected, and understandable), and
decided to be abstinent to `set`.
I double checked the full RFC discussion.
You asked four times explicitly, and one time indirectly, to allow
`set` but not `get`.
Would you mind to elabora
On Mon, Jul 7, 2025 at 12:53 PM Eric Norris wrote:
>
> On Wed, Jul 2, 2025 at 11:48 AM Eric Norris wrote:
> >
> > > Based on the feedback so far (I do plan on waiting for more responses
> > > to your email), and on my own preferences, I wonder if there is a
> > > hybrid option I could propose. Pe
On 21.07.25 00:05, Hanz wrote:
Hello, my two cents,
On Thu, Jun 19, 2025 at 9:09 PM Marc Bennewitz wrote:
Hi,
During the discussion about the year 2038 issue it turned out that
maybe
it's time to drop support for 32-bit of PHP completely.
Based on that I have created an
Hi everyone,
On 19.06.25 16:08, Marc Bennewitz wrote:
Hi,
During the discussion about the year 2038 issue it turned out that
maybe it's time to drop support for 32-bit of PHP completely.
Based on that I have created an RFC to deprecate 32-bit build in
8.next and drop support for it in 9.
Hey all,
>> It's important to plan for the future and come up with a holistic solution.
>> I don't want to end up in a situation where in hindsight we shouldn't have
>> allowed a "set hook" for example and should've just left readonly alone.
>
> I honestly cannot come up with a reason for why th
Hi internals,
Any *RFCs* that are trying to target PHP 8.5 need to have completed voting
by August 12, 3 weeks from tomorrow. This lets us finalize the list of the
biggest features that need to be merged. For smaller features *that do not
require an RFC*, they can still be proposed and implemented
On Thu, Jul 17, 2025 at 9:21 AM Daniel Scherzer
wrote:
> Hi internals,
>
> Voting is now open for this RFC.
>
> * RFC: https://wiki.php.net/rfc/delayedtargetvalidation_attribute
> * Discussion thread: https://externals.io/message/127702
>
> Voting will end 2025-07-31 at end-of-day UTC.
>
> -Danie
Le lun. 21 juil. 2025 à 20:23, Daniel Scherzer
a écrit :
> On Thu, Jul 17, 2025 at 9:21 AM Daniel Scherzer <
> daniel.e.scher...@gmail.com> wrote:
>
>> Hi internals,
>>
>> Voting is now open for this RFC.
>>
>> * RFC: https://wiki.php.net/rfc/delayedtargetvalidation_attribute
>> * Discussion thre
20 matches
Mail list logo
