On Sat, Sep 7, 2024, at 12:07 PM, Rowan Tommins [IMSoP] wrote:
> On 7 September 2024 17:23:13 BST, Davey Shafik wrote:
>>
>>My point is that if you talk about type DEFs, you now have this feature where
>>you can input one type and get something that encapsulates it, and it seems
>>weird that enu
On 7 September 2024 17:23:13 BST, Davey Shafik wrote:
>
>My point is that if you talk about type DEFs, you now have this feature where
>you can input one type and get something that encapsulates it, and it seems
>weird that enums would LOOK similar In type hint usage and function
>differentl
> On Sep 7, 2024, at 06:28, Larry Garfield wrote:
>
> On Fri, Sep 6, 2024, at 7:46 PM, Davey Shafik wrote:
>
>> My main struggle with this is readability. As much as I want custom
>> types (and type aliases is a good chunk of the way there), the main
>> issue I have is understanding what the
On Sat, Sep 7, 2024, at 15:28, Larry Garfield wrote:
> On Fri, Sep 6, 2024, at 7:46 PM, Davey Shafik wrote:
>
> > My main struggle with this is readability. As much as I want custom
> > types (and type aliases is a good chunk of the way there), the main
> > issue I have is understanding what t
> On Sep 7, 2024, at 9:28 AM, Rob Landers wrote:
> Keep in mind there is already single-class aliasing with well-known behavior
> for both local and project-wide aliases. Local aliases are done through 'use'
> statements, and project-wide aliases can be created by using the
> `class_alias()` fu
On Sat, Sep 7, 2024, at 14:42, Mike Schinkel wrote:
> > On Sep 6, 2024, at 4:45 PM, Larry Garfield wrote:
> > Aliases can then be used only in parameter, return, property, and
> > instanceof types. Extends and implements are out of scope entirely.
>
> Is there a strong technical reason why exte
On Fri, Sep 6, 2024, at 7:46 PM, Davey Shafik wrote:
> My main struggle with this is readability. As much as I want custom
> types (and type aliases is a good chunk of the way there), the main
> issue I have is understanding what the valid inputs are:
>
> function foo(Status $string): void { }
>
On Sat, Sep 7, 2024, at 7:42 AM, Mike Schinkel wrote:
>> On Sep 6, 2024, at 4:45 PM, Larry Garfield wrote:
>> Aliases can then be used only in parameter, return, property, and instanceof
>> types. Extends and implements are out of scope entirely.
>
> Is there a strong technical reason why extend
> On Sep 6, 2024, at 4:45 PM, Larry Garfield wrote:
> Aliases can then be used only in parameter, return, property, and instanceof
> types. Extends and implements are out of scope entirely.
Is there a strong technical reason why extends and implements should be out of
scope?
There is definit
On Sat, Sep 7, 2024, at 05:17, Juliette Reinders Folmer wrote:
> On 6-9-2024 20:41, Rob Landers wrote:
>> - This RFC expands the "use ... as ..." syntax to allow any type expression
>> on the left side. These aliases are PER FILE and expire once the file is
>> compiled.
>>
>
> Explicitly withou
10 matches
Mail list logo
