Hi, internals.
I started vote to RFC grapheme_levenshtein
RFC: https://wiki.php.net/rfc/grapheme_levenshtein
Voting end is 2025-04-16 00:00:00(UTC+0).
Regards
Yuya
--
---
Yuya Hamada (tekimen)
- https://tekitoh-memdhoi.info
- https://github.com/youkidearitai
---
On 31/03/2025 21:38, Ilija Tovilo wrote:
Hi everyone
A few years ago, an RFC was proposed to introduce special syntax for
self-referencing closures, mainly used for implementing recursion.
https://wiki.php.net/rfc/closure_self_reference
The proposed solution allows specifying a variable that w
On Tue, Apr 1, 2025, 01:03 Niels Dossche wrote:
> Hi internals!
>
> I'm excited to share what I've been working on!
> I had an epiphany. I realized what we truly need to revolutionize PHP: a
> new operator.
>
> Hear me out.
> We live in an imperfect world, and we often approximate data, but neith
Hi Larry,
On Fri, Mar 28, 2025 at 7:48 PM Larry Garfield
wrote:
> I have to think people are misunderstanding Nikita's earlier comment, or
> perhaps that he phrased it poorly.
>
> The determination of whether a method call is type-compatible with the
> parameters passed to it is made *at runtime
On 2025-04-01 09:38, Ilija Tovilo wrote:
> Hi everyone
>
>
> This is essentially already possible through a by-reference capture.
>
> $fibonacci = function (int $n) use (&$fibonacci) { ... };
>
> This cannot be a by-value capture because by the time the closure is
> created and variables are bou
On 31/03/2025 23:03, Niels Dossche wrote:
Hi internals!
I'm excited to share what I've been working on!
I had an epiphany. I realized what we truly need to revolutionize PHP: a new
operator.
Hear me out.
We live in an imperfect world, and we often approximate data, but neither `==`
nor `===`
Hello Ilija,
Nice addition! I thought about edge cases and what the desired output is
with nested closures?
Example:
On Mon, Mar 31, 2025, at 21:45, Rob Landers wrote:
> Hello internals,
>
> I have significantly revamped the RFC (again). Key changes to the RFC:
>
> 1. More (realistic) examples,
> 2. Since enums are basically specialized classes, they are allowed to be
> nested as well (hat tip to Reddit),
> 3.
Hello internals,
I have significantly revamped the RFC (again). Key changes to the RFC:
1. More (realistic) examples,
2. Since enums are basically specialized classes, they are allowed to be nested
as well (hat tip to Reddit),
3. Using backslash as the class separator,
4. Proper scoping (and sha
On 30/03/2025 22:53, Ignace Nyamagana Butera wrote:
On 30/03/2025 14:42, Tim Düsterhus wrote:
Hi
Am 2025-03-27 23:49, schrieb Ignace Nyamagana Butera:
Hi Máté,
for RFC 3986:
https://datatracker.ietf.org/doc/html/rfc3986#section-5.3), and then
this string is parsed and validated. Unfo
10 matches
Mail list logo
