Project Static Analyzer says that developrs are open to feature requests so here's one. From my experience violations of static initialization order are rather common in large databases and many compilers don't issue any warnings on this. This causes hard to find bugs when changing compiler or version which aren't easily detectable.
Adding this check seems to be rather trivial (I guess I could even add myself when I have time) but may have tremendous benefit for C++ community (and probably for Clang itself because AFAIK there are no open-source compilers/analyzers doing anything like this).
Extended Description
Project Static Analyzer says that developrs are open to feature requests so here's one. From my experience violations of static initialization order are rather common in large databases and many compilers don't issue any warnings on this. This causes hard to find bugs when changing compiler or version which aren't easily detectable.
Adding this check seems to be rather trivial (I guess I could even add myself when I have time) but may have tremendous benefit for C++ community (and probably for Clang itself because AFAIK there are no open-source compilers/analyzers doing anything like this).