On Sat, Dec 26, 2020 at 10:02 AM Niklas Keller wrote:
>>
>> I want to re-iterate my opinion on this discussion thread: anything
>> with a prefix is a hard-no from me. Namespaces are literally designed
>> for this, and I will not vote "yes" to `iter_all`, `iterable_all`,
>> etc, no matter what the
>
> I want to re-iterate my opinion on this discussion thread: anything
> with a prefix is a hard-no from me. Namespaces are literally designed
> for this, and I will not vote "yes" to `iter_all`, `iterable_all`,
> etc, no matter what the prefix is. Anything without a namespace is a
> no from me.
Hi Levi,
> I want to re-iterate my opinion on this discussion thread: anything
> with a prefix is a hard-no from me. Namespaces are literally designed
> for this, and I will not vote "yes" to `iter_all`, `iterable_all`,
> etc, no matter what the prefix is. Anything without a namespace is a
> no
On Tue, 22 Dec 2020 at 16:21, Larry Garfield wrote:
> That's why I am OK with most options except `iterable_`, because that's a
> lot of needless typing.
>
Whether the prefix is iterable or iter or just i, I'll always be typing
iany and hitting enter, letting my IDE do the leg work, avoiding
On Sat, Dec 19, 2020 at 1:24 PM tyson andre wrote:
>
> Hi internals,
>
> I've created a straw poll for the naming pattern to use for `*any()` and
> `*all()` on iterables.
> https://wiki.php.net/rfc/any_all_on_iterable_straw_poll
>
> Background: The RFC
Le 22/12/2020 à 16:27, tyson andre a écrit :
Hi Pierre,
This is the kind of reasoning I fully support usually, I do maintain a
few libraries for multiple PHP versions as most people in this list and
make things easily polifyllable is something I'm sensible to.
Nevertheless, the language and
Hi Pierre,
> This is the kind of reasoning I fully support usually, I do maintain a
> few libraries for multiple PHP versions as most people in this list and
> make things easily polifyllable is something I'm sensible to.
>
> Nevertheless, the language and its standard library has to evolve at
On Tue, 22 Dec 2020 at 16:05, tyson andre wrote:
> Hi Marco,
>
> >Hey Tyson,
> >
> > I know I'm being stubborn, but we have namespaces, but also an "old
> guard" that doesn't understand its own programming language 路♀️
>
> I assume it's a case of not liking them or assuming others wouldn't like
Hi Marco,
>Hey Tyson,
>
> I know I'm being stubborn, but we have namespaces, but also an "old guard"
> that doesn't understand its own programming language 路♀️
I assume it's a case of not liking them or assuming others wouldn't like them
instead of not understanding them.
Namespaces for
Fully agree with Marco
On Tue, Dec 22, 2020, 1:00 PM Marco Pivetta wrote:
> Hey Tyson,
>
> I know I'm being stubborn, but we have namespaces, but also an "old guard"
> that doesn't understand its own programming language 路♀️
>
> On Sat, Dec 19, 2020, 21:24 tyson andre wrote:
>
> > Hi
Hey Tyson,
I know I'm being stubborn, but we have namespaces, but also an "old guard"
that doesn't understand its own programming language 路♀️
On Sat, Dec 19, 2020, 21:24 tyson andre wrote:
> Hi internals,
>
> I've created a straw poll for the naming pattern to use for `*any()` and
> `*all()`
Le 22/12/2020 à 01:48, tyson andre a écrit :
Hi Sara Golemon,
This is probably going to be a terrible idea because it involves a little magic
but...
"iterable" is already a forbidden userspace class name since it's reserved for
the psuedo-type which is a union of `Traversable | array`.
Hi Sara Golemon,
> This is probably going to be a terrible idea because it involves a little
> magic but...
>
> "iterable" is already a forbidden userspace class name since it's reserved
> for the psuedo-type which is a union of `Traversable | array`.
>
> What if we went ahead and defined an
On Sat, Dec 19, 2020 at 2:24 PM tyson andre
wrote:
> I've created a straw poll for the naming pattern to use for `*any()` and
> `*all()` on iterables.
> https://wiki.php.net/rfc/any_all_on_iterable_straw_poll
>
>
This is probably going to be a terrible idea because it involves a little
magic
Hi internals,
I've created a straw poll for the naming pattern to use for `*any()` and
`*all()` on iterables.
https://wiki.php.net/rfc/any_all_on_iterable_straw_poll
Background: The RFC https://wiki.php.net/rfc/any_all_on_iterable proposes
adding only two functions,
but more functionality
15 matches
Mail list logo
