Don't just moan about the syle, coerce the source

[MatthewHambley]

Some style rules require additional information which only the developer could know. However many have an obvious
default or otherwise implied modification associated with them. For instance, when checking that implicit statements are used throughout, we might assume that if one is missing it could be added.

This moves from simply inspecting the source to modifying it which brings up questions of correctness but it is still an interesting thing to consider.

[MatthewHambley]

Obvious candidates for coercion:

• MissingImplicit - If no implicit statement is found, add one with a user defined option, default to none.
• MissingPointerInit - If no pointer initialisation is found add one to null().