Add output of the received and expected types for messages that indicate type differences
With the MISRA 2012 "essential type" implementation, we often see messages that indicated "Expression assigned to a narrower or different essential type" or "Composite expression with smaller essential type than other operand". For these types of messages that indicate a discrepancy of type, it would help in debugging these messages if the types involved could be added into the output.
Robert Slaymaker commented
Definitely gets my vote--this would be quite helpful when linting macro-based code or complex expressions after they're written.
I've also wished for a similar enhancement to some older , non-Misra related messages. It seems now like many of them do. I don't know if this has been addressed in the older messages since I first thought of it.