Re: [PHP-DEV] Proposal: Support for RFC4648 in PHP

2025-06-12 Thread Ayesh Karunaratne
> > Why do it in core? > Is userland base16/base32 performance unsatisfactory? Even if the performance is satisfactory, having this in core can help user-land code to get rid of their own implementations (which they often do, to be URL-safe, for example). I imagine native implementations can make

Re: [PHP-DEV] Proposal: Support for RFC4648 in PHP

2025-06-12 Thread Hans Henrik Bergan
On Thu, 12 Jun 2025 at 18:53, ignace nyamagana butera wrote: > > Greetings, > > I have been playing around with an RFC proposal for some time and recently > after discussing it with Tim Düsterhus he has volunteered > to do the implementation so I would like to submit to you an RFC around data >

[PHP-DEV] Proposal: Support for RFC4648 in PHP

2025-06-12 Thread ignace nyamagana butera
Greetings, I have been playing around with an RFC proposal for some time and recently after discussing it with Tim Düsterhus he has volunteered to do the implementation so I would like to submit to you an RFC around data encoding in PHP. The goal of the RFC is to fully implement RFC4648 (base16 ,

Re: [PHP-DEV] [VOTE] Clone with v2

2025-06-12 Thread Tim Düsterhus
Hi Am 2025-06-11 21:37, schrieb Andreas Hennings: While these are valid arguments, I don't know that the other thread had enough time to settle and agree on this array syntax. The last time I looked at it, it still had the named arguments. (Unfortunately I don't have permissions to see the RFC e

Re: [PHP-DEV] [VOTE] Clone with v2

2025-06-12 Thread Tim Düsterhus
Hi Am 2025-06-11 22:09, schrieb Andreas Hennings: Calling __clone() afterward would mean the new properties would already be set and the old ones gone, contrasting existing behavior and thus users' expectations. But in fact both of the following sentences are true: - Currently, no further cha