Re: [PHP-DEV] Module or Class Visibility, Season 2

2025-05-31 Thread Alwin Garside
On 30 May 2025, at 21:29, Rowan Tommins [IMSoP] wrote: > > On 30 May 2025 19:21:08 BST, Alwin Garside wrote: >> In the example above, I image calling or extending the `Foo::bar()` method >> from somewhere outside the `Acme` namespace would trigger an E_USER_WARNING >&g

Re: [PHP-DEV] Module or Class Visibility, Season 2

2025-05-30 Thread Alwin Garside
On 30 May 2025, at 18:38, Rowan Tommins [IMSoP] wrote: > > On 30 May 2025 08:57:34 BST, Rob Landers wrote: >> >> I’m starting to think that maybe modules might be a bad idea; or at least, >> class/module visibility. >> >> As an anecdote, I was looking to extract a protobuf encoding library fr

Re: [PHP-DEV] Module or Class Visibility, Season 2

2025-05-26 Thread Alwin Garside
Hey all, It took me a while, but I'm finally caught up with this thread, and would like to give my 2 cents. On 25 May 2025, at 23:17, Rowan Tommins [IMSoP] wrote: > > On 25/05/2025 21:28, Larry Garfield wrote: >> Even if we develop some way such that in Foo.php, loading the class >> \Beep\Boo

Re: [PHP-DEV] [RFC] Add num_available_processors

2025-05-25 Thread Alwin Garside
On 24 May 2025, at 20:48, Rob Landers wrote: > > On Sat, May 24, 2025, at 19:37, Daniel Kesselberg wrote: >> >> >> Hi everyone, >> >> I'm happy to share my first RFC :) It proposes adding a small function >> to retrieve the number of available processors; a feature that's >> commonly found i

Re: [PHP-DEV] Forced named parameters

2025-05-23 Thread Alwin Garside
Hi Anton, > On 23 May 2025, at 03:24, Anton Smirnov wrote: > >> Moreover, what if I don't need a variadic parameter, but would like to >> declare that the function's interface requires named arguments (because I >> don't want to be tied to locking parameters to specific positions). > > If you

Re: [PHP-DEV] Vibe check: array shapes

2025-03-01 Thread Alwin Garside
On 1 Mar 2025, at 08:37, Rob Landers wrote: > > Hi Alwin, > > You may be interested in http://wiki.php.net/rfc/records, whose goal from the > beginning was a new type that behaved like arrays (value semantics, copy on > write) as well as the ability to attach behavior to them. > > I’ve since

Re: [PHP-DEV] Vibe check: array shapes

2025-02-28 Thread Alwin Garside
On 1 Mar 2025, at 00:28, Larry Garfield wrote: > Your friends are correct. Arrays in PHP are an awful thing. They are twice > as memory hungry as objects, they provide no static guarantees, and they're a > security hole waiting to happen (and has in fact happened). > > And since PHP 8.0, *we

Re: [PHP-DEV] Vibe check: array shapes

2025-02-28 Thread Alwin Garside
On 1 Mar 2025, at 00:28, Tim Düsterhus wrote: > >> Anyway, I would love to try and push this idea forward – either by >> contacting Kacpar, or writing my own RFC – and have a shot at implementing a >> proof of concept, but first I would like to get a feel for whether this >> proposal would fin

Re: [PHP-DEV] Vibe check: array shapes

2025-02-28 Thread Alwin Garside
> On 28 Feb 2025, at 23:57, Bilge wrote: > > Generics Yes, I am aware that generics are being worked on. However, generics wouldn't provide structural interfaces for arrays. At most it would provide a way to infer/define generic types for array keys and/or values. I guess I should've provi

[PHP-DEV] Vibe check: array shapes

2025-02-28 Thread Alwin Garside
P, and perhaps read the draft written by Kacper Donat [1] for a much more eloquent example of what I'm trying to propose here. Thank you all very much in advance. Kindest regards, Alwin Garside [1] https://hackmd.io/@kadet/php-rfc-shapes