Description:
------------
Typehints are means to introduce typesafety into PHP code which should futher improve the code reliability and robustness.

Considering that PHP language is dynamic in nature it's difficult to fulfill the promise completely as there's no compilation stage that integrates calling code with the modules that might make extensive usage of the hint.

Failing to satisfy the expectations of typehints generates a fatal error though.
Unfortunately it can only be detected at runtime and that can be very late when the misfortunate code path is executed - at edge case never.

The most real usage of the typehints are made by advanced IDE like Eclipse PDT or PhpStorm which use it to provide advanced intellisense like code completition and near compile quality static code analisis. In those development environments similar effect can be achieved by adding a proper phpdoc annotation block before the method signature. It's much more verbose though and naturally a typehint is a very succinct replacement and it's where I see the most value of the typehints.

Given the above please consider replacing the current behavior of throwing a fatal error in case of a mismatch by just emitting a warning.