Moving away from introducing any issue - extra functionality needed?

[pjljvandelaar]

Since human resource are typically scarce within organizations,
we are preferring only to change when we are absolutely certain that no compiler error or warning is introduced.

Consequently, our users might not be exposed to some rewrites that would otherwise educate them on particular Ada constructions.

Furthermore, some changes are not done since we lack the possibility to do post processing.
For example, replacing

  if X.Length > 0 then ...

by

  if not X.Is_Empty then ...

can introduce a compiler warning when this was the only location where operators on Count_Type where used,
and thus the with/use clause becomes obsolete.

Instead of prevent these rewrites should we add some post processing capabilities, e.g. on the changed file,
to ensure it still compiles without warnings?

[pjljvandelaar]

Or should we aim for the 80 -20 rule?
With little effort most changes are correct.
The ones who fail, need considerably less manual effort...