Ivijan (Stefan) Stipic the question to me is why check the contract inside of the method ? -> enforce it before ! -> function set_orders_id(int $id): int

that's how I code at least. you could ofc add a fair amount of if conditions but I like my ruleset strickt so I don't make to many mistakes and php5 is already deprecated.

but you're right it's a good example where it would make sense in <php7

j Well, I give that like example. Is better to use strict rules inside function arguments but imagine that we expect in that function integer, boolean, float and string. Integer is for ID, float is for price, boolean is for email send and string is for some message. We can use same funcion and simple if/else to separate data and use same function for various things. Is stupid example but I figureout it before some times where I was forced to use same string for various data like I decribe above. In that my problem I was not able to add additional argument or aditional string, just must expect something from database and do with that how I know and separate it properly.

I first time use this in my 14 years of practice.

Ivijan (Stefan) Stipic I think it's a good example, esp if we don't use "declare(strict_types=true)" in all files! :) assertion is always better than assumption in my opinion ! :)