Currently the build is failing in some parts of the codebase that are
obviously affected in some way.
I ran valgrind for couple of failing tests and I got numerous reports about
memory leaks and conditional jumps over uninitialized values.
Not sure what is the reason for that, I had merge conflict with upstream
master couple days ago, might be a reason.

I would appreciate if anyone could give me hand on this ?

On Feb 26, 2018 1:48 PM, "Silvio Marijić" <marijic.sil...@gmail.com> wrote:

> Currently the build is failing in some parts of the codebase that are
> obviously affected in some way.
> I ran valgrind for couple of failing tests and I got numerous reports
> about memory leaks and conditional jumps over uninitialized values.
> Not sure what is the reason for that, I had merge conflict with upstream
> master couple days ago, might be a reason.
>
> I would appreciate if anyone could give me hand on this ?
>
> On Feb 26, 2018 1:44 PM, marijic.sil...@gmail.com wrote:
>
> Yes, I've also took that into consideration when choosing keyword.
>
> On Feb 26, 2018 11:35 AM, "Crocodile" <crocodil...@gmail.com> wrote:
>
> Is "value" or "immutable" going to become a new reserved word? Ain't we
> going to have some BC breaks because of that? If so, then "value" is going
> to bring more BC breaks then "immutable".
>
> On Sun, Feb 25, 2018 at 8:02 PM Paul Jones <pmjone...@gmail.com> wrote:
>
>>
>>
>> > On Feb 25, 2018, at 12:59, Silvio Marijić <marijic.sil...@gmail.com>
>> wrote:
>> >
>> > Here is link to tweet https://twitter.com/SilvioMari
>> jic/status/965564630071300096
>>
>> After having read that, I think "immutable" is still perfectly reasonable.
>>
>>
>> --
>> Paul M. Jones
>> pmjo...@pmjones.io
>> http://paul-m-jones.com
>>
>> Modernizing Legacy Applications in PHP
>> https://leanpub.com/mlaphp
>>
>> Solving the N+1 Problem in PHP
>> https://leanpub.com/sn1php
>>
>>
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>> --
> Best regards,
> Victor Bolshov
>
>
>
>

Reply via email to