I feel conflicted about this. On the one hand, lldb's build has significantly more warnings than LLVM and Clang, so it would be great to clean this up. On the other hand, I've been bitten by libraries that have this enabled in release builds because compilers introduce new warnings. I think I would be fine with this if it were not enabled in tagged releases (not sure how to do that though).
On Thu, Aug 14, 2014 at 1:38 PM, Zachary Turner <[email protected]> wrote: > What would it take to enable warnings as errors on all platforms? > > I've done alot of work getting the windows build warning free, but it seems > like very time I sync the code on linux or Mac, there's many many new > warnings introduced. I'm always vigilant about fixing warnings in my own > code, it would be nice if everyone else had the same level of vigilance. If > warnings broke the build, then I think that would be a good motivator to fix > your warnings. > > Thoughts? > > _______________________________________________ > lldb-dev mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
