Skip to content

Consider final in combination with protected to exclude some code analysis scenarios #31

@Ocramius

Description

@Ocramius

As discussed in person with @asgrim and @akrabat, the following change is not a BC break, because final already makes it impossible to rely on protected properties:

final class Foo
{
    protected $bar = 'baz';
}

changed into:

final class Foo
{
    private $bar = 'baz';
}

This kind of scenario is tricky to represent correctly with the current design of the Comparator

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions