SP's 'out' parameter issue when doesn't match IN and OUT data type.

When make a SP, we can set 'OUT' type argument that to return multiple results. But, for example, when a caller declare smallint, but the caller SP's OUT data type declared as double,
totally break thread stack frame. especially multiply declare dozen or hundred OUT arguments.
But kind of '@xxxxxxxxx' session variable used/passed for the return arguments seem no problem that seem automatically detects byte size and so while local decleared variable does not.

What my point is (of cause stack frame breaking is a possibly be normal/expected behavior),
but automatically detect whether wrong type or make warning message before forcely over write stack buffer of the return values since it actually break thread stack frame.