[5.2] Blade push with layouts weird ordering

[mark86092]

Original issue #12753

In this PR, fix the weird results in #12753.
After the fix, the results below is much more like what the "push" do

b0  c1  c2

Template:

>> a.blade.php
@stack('me')
>> b.blade.php
@extends('a')
@push('me') b0 @endpush('me')
>> c.blade.php
@extends('b')
@push('me') c1 @endpush('me')
@push('me') c2 @endpush('me')

This PR try to modify the $sections array, let the @push to save its state according to the renderNumber

There some drawbacks:

1. People may manually modify their template, but this PR brokes their view
2. They must clean their compiled view
3. I have no idea how the test codes should be, at least I test on a runnig server

[GrahamCampbell]

missing newline

[crynobone]

They must clean their compiled view

Shouldn't thing like this target 5.3/master branch.

[GrahamCampbell]

Shouldn't thing like this target 5.3/master branch.

Hmmm. Is there a way to do this in a non-breaking way, so clearing will only be needed to fix the bug? We don't really want to break stuff on 5.3 unnecessarly either.

[mark86092]

Actually, the internal structure of $sections is changed, all other behavior should be the same.

If the $sections structure keeps, I have to think another way, need trying.

[taylorotwell]

Closing since breaking.

[mark86092]

@taylorotwell what's your suggestion? goto 5.3 or try non-breaking way or do nothing?