On Sun, Feb 14, 2021 at 5:51 PM Levi Morrison
wrote:
>
> Oof, this is a long one. I'm going to snip some of it but respond to
> most things privately; I will also respond to some things publicly
> later.
>
> On Sun, Feb 14, 2021 at 3:44 PM tyson andre wrote:
> >
> > Hi internals,
> >
> > > >
Oof, this is a long one. I'm going to snip some of it but respond to
most things privately; I will also respond to some things publicly
later.
On Sun, Feb 14, 2021 at 3:44 PM tyson andre wrote:
>
> Hi internals,
>
> > > 1b. We may switch the direction of this alias in 9.0.
>
> The new names for
Hi internals,
> > 1b. We may switch the direction of this alias in 9.0.
The new names for existing Spl types at least seem more readable and possible
to polyfill with `class_alias`.
It should be clarified if "data types" include interfaces such as
On Sat, Feb 13, 2021 at 10:57 AM Pierre R. wrote:
>
> Le 13/02/2021 à 18:01, Levi Morrison via internals a écrit :
> > You make some good points, Pierre. Here are my main rebuttals:
> >
> > 1. "Spl" is already the effective namespace for the SPL because
> > that's the prefix used by
Le 13/02/2021 à 18:01, Levi Morrison via internals a écrit :
You make some good points, Pierre. Here are my main rebuttals:
1. "Spl" is already the effective namespace for the SPL because
that's the prefix used by SplFixedArray, SplQueue, spl_classes, and so
on. Its namespace has already been
On Sat, Feb 13, 2021 at 9:25 AM Pierre wrote:
>
> Le 11/02/2021 à 18:48, Chase Peeler a écrit :
> > I think Spl makes sense (there might be a debate over whether it should be
> > Spl or SPL though). How feasible is it to create generate a deprecation
> > notice when the global version is used? I
Le 11/02/2021 à 18:48, Chase Peeler a écrit :
I think Spl makes sense (there might be a debate over whether it should be
Spl or SPL though). How feasible is it to create generate a deprecation
notice when the global version is used? I assume the hope is to eventually
move away from using those,
On Thu, Feb 11, 2021 at 1:08 PM Lynn wrote:
>
>
> On Thu, Feb 11, 2021 at 6:55 PM Levi Morrison via internals <
> internals@lists.php.net> wrote:
>
>> I don't know the answer to that question. However, I don't think we
>> should add a deprecation on the very first version that we add the
>>
On Thu, Feb 11, 2021 at 6:55 PM Levi Morrison via internals <
internals@lists.php.net> wrote:
> I don't know the answer to that question. However, I don't think we
> should add a deprecation on the very first version that we add the
> aliases anyway. I think that would make for a bad upgrade
On Thu, Feb 11, 2021 at 10:48 AM Chase Peeler wrote:
>
>
>
> On Thu, Feb 11, 2021 at 12:23 PM Levi Morrison via internals
> wrote:
>>
>> On Thu, Feb 11, 2021 at 9:57 AM Mark Randall wrote:
>> >
>> > On 11/02/2021 16:39, Levi Morrison wrote:
>> > > Let me know what you think. I am hopeful this
On Thu, Feb 11, 2021 at 12:23 PM Levi Morrison via internals <
internals@lists.php.net> wrote:
> On Thu, Feb 11, 2021 at 9:57 AM Mark Randall wrote:
> >
> > On 11/02/2021 16:39, Levi Morrison wrote:
> > > Let me know what you think. I am hopeful this approach will work
> because:
> > > 1. It
On Thu, Feb 11, 2021 at 9:57 AM Mark Randall wrote:
>
> On 11/02/2021 16:39, Levi Morrison wrote:
> > Let me know what you think. I am hopeful this approach will work because:
> > 1. It is focused on a specific area which already has an established
> > "namespace", but in name-only (not
On 11/02/2021 16:39, Levi Morrison wrote:
Let me know what you think. I am hopeful this approach will work because:
1. It is focused on a specific area which already has an established
"namespace", but in name-only (not technically).
2. It does not try to solve the larger problem, which has
13 matches
Mail list logo
