a good starting point would be to make the warnings a lot more
self-explanatory. Right now it's often non-obvious trying to figure out
how the dependencies are structured and which one should be changed to
get rid of the bug.
a good way i see is to:
- improve the debug output so that it's obvious at a glance what the
problem is.
- quickly reach a close-to-100%-perfect stage, brute-force. Drop
__init* annotations en masse if they are not perfectly layered.
Whoever reintroduces them will then have to do it perfectly.
- then turn these into hard failures (which they _are_ in a significant
percentage of the situations).
once it's a hard build failure, people will fix them quickly and
automated tests will pick them up as well.
Ingo
--
