I wouldn't agree this is an improvement - the toString on SizeExpression currently returns an invalid and misleading value. It also seems wise to apply this to 4.x rather than it being delayed until 5.x (since the reason I am submitting this fix is that I wasted a lot of time trying to track down a bug I thought was elsewhere due to the misleading toString on SizeExpression)