Description:
------------
According to PHP manual:
"If a trait defines a property then a class can not define a property with the same name unless it is compatible (same visibility and initial value), otherwise a fatal error is issued. Before PHP 7.0.0, defining a property in the class with the same visibility and initial value as in the trait, raised an E_STRICT notice. "
but it seems it's not completely true. Some casts are done, so in fact you can use different value.
Test script:
---------------
trait PropertiesTrait
{
public $same = true;
public function message()
{
if ($this->same === true) {
return "A";
}
return "B";
}
}
class PropertiesExample
{
use PropertiesTrait;
public $same = 2;
}
$example = new PropertiesExample();
echo $example->message();
Expected result:
----------------
Fatal error as described in documentation.
Actual result:
--------------
B (Same result is for PHP 7.1.1). No warning/notice is generated

The conflict detection logic uses zend_operator's compare_function, which does loose comparisons. The original RFC doesn't say whether to be strict or loose but I think the intention is that it would be strict.