Hi internals,
On experimenting with return type-hints I noted an inconsistency on
overwriting an existing hint to a more specific one. On adding a non
existing return type-hint on overwrite it's fine but it's logically the
same (this previously was an E_STRICT).
http://3v4l.org/YdB8s -
Marc,
On Wed, Apr 1, 2015 at 2:46 PM, Marc Bennewitz dev@mabe.berlin wrote:
Hi internals,
On experimenting with return type-hints I noted an inconsistency on
overwriting an existing hint to a more specific one. On adding a non
existing return type-hint on overwrite it's fine but it's
Hi Anthony,
Am 01.04.2015 um 21:25 schrieb Anthony Ferrara:
Marc,
On Wed, Apr 1, 2015 at 2:46 PM, Marc Bennewitz dev@mabe.berlin wrote:
Hi internals,
On experimenting with return type-hints I noted an inconsistency on
overwriting an existing hint to a more specific one. On adding a non
Thank you for the really helpful explanation!
Now I understand the reasons but I don't have enough experience in C or the
engine to make that possible.
Would it be possible to support it in the first place only if the return
type hints are already known by the engine?
If my memory is working
