Den 2019-07-05 kl. 03:48, skrev Theodore Brown:
On Thu, July 4, 2019 at 5:26 PM Björn Larsson wrote:
Den 2019-07-03 kl. 17:25, skrev Peter Bowyer:
Thanks for taking the time to push forward this RFC.
I found the earlier discussion at https://externals.io/message/104744,
which I hadn't seen.
> > > Thanks for taking the time to push forward this RFC.
> > >
> > > I found the earlier discussion at https://externals.io/message/104744,
> > > which I hadn't seen. Like others, I would have chosen to keep {} for
> > > string offsets to make it clearer, though I have not used {} in my
>
On Thu, July 4, 2019 at 5:26 PM Björn Larsson wrote:
> Den 2019-07-03 kl. 17:25, skrev Peter Bowyer:
>
> > Thanks for taking the time to push forward this RFC.
> >
> > I found the earlier discussion at https://externals.io/message/104744,
> > which I hadn't seen. Like others, I would have chosen
Den 2019-07-03 kl. 17:25, skrev Peter Bowyer:
Hi Andrey,
Thanks for taking the time to push forward this RFC.
I found the earlier discussion at https://externals.io/message/104744,
which I hadn't seen. Like others, I would have chosen to keep {} for string
offsets to make it clearer, though I h
Den 2019-07-03 kl. 19:22, skrev Claude Pache:
Le 3 juil. 2019 à 17:59, Nikita Popov a écrit :
On Wed, Jul 3, 2019 at 4:41 PM Levi Morrison wrote:
Was any analysis of usage done for top open source projects? I support
this direction, but would prefer to know its current impact before
votin
On Wed, July 3, 2019 at 10:59 AM Nikita Popov wrote:
> On Wed, Jul 3, 2019 at 4:41 PM Levi Morrison wrote:
>
> > Was any analysis of usage done for top open source projects? I support
> > this direction, but would prefer to know its current impact before
> > voting.
>
>
> I checked top 2k pro
> Le 3 juil. 2019 à 17:59, Nikita Popov a écrit :
>
> On Wed, Jul 3, 2019 at 4:41 PM Levi Morrison wrote:
>
>> Was any analysis of usage done for top open source projects? I support
>> this direction, but would prefer to know its current impact before
>> voting.
>>
>
> I checked top 2k pro
On 7/3/2019 7:41 AM, Levi Morrison wrote:
Was any analysis of usage done for top open source projects? I support
this direction, but would prefer to know its current impact before
voting.
Well, I currently use braces when I iterate over strings for reasons of
readability.
Example:
https://g
On Wed, Jul 3, 2019 at 4:41 PM Levi Morrison wrote:
> Was any analysis of usage done for top open source projects? I support
> this direction, but would prefer to know its current impact before
> voting.
>
I checked top 2k projects with a 2-3 months outdated data set. Here is the
analysis log: h
Hi Andrey,
Thanks for taking the time to push forward this RFC.
I found the earlier discussion at https://externals.io/message/104744,
which I hadn't seen. Like others, I would have chosen to keep {} for string
offsets to make it clearer, though I have not used {} in my code for a
decade. Was any
Was any analysis of usage done for top open source projects? I support
this direction, but would prefer to know its current impact before
voting.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 7/3/2019 3:18 AM, Andrew Gromov wrote:
Hello Internals,
I just started the vote on
https://wiki.php.net/rfc/deprecate_curly_braces_array_accessand I will
close it in two weeks from now (10.06.2019).
Thanks in advance to all who paid attention to the vote.
Best regards, Andrey.
The URL
On Wed, 3 Jul 2019 at 12:18, Andrew Gromov wrote:
> Hello Internals,
>
>
> I just started the vote on
> https://wiki.php.net/rfc/deprecate_curly_braces_array_accessand I will
> close it in two weeks from now (10.06.2019).
>
> Thanks in advance to all who paid attention to the vote.
>
> Best regar
13 matches
Mail list logo