ChuanqiXu9 wrote: > > This is the C++'s ecosystem in the open ended world. Image a situation that > > we're using a third party module and we add a new option to our library, > > then the build bails out! > > I think this is the correct behavior if the incompatibility caused by said > option could cause issues down the line (compile errors, linking errors, > runtime errors), all of which will be a lot more confusing and harder to > understand to the user. > > Also, perhaps relevant: > https://github.com/build2/HOWTO/blob/master/entries/compile-options-in-buildfile.md
Yeah, we will still emit warnings to let users know what happened. It's the user's responsibility if the user silent the warning. Let the user pay what they do. And there are a lot of false positive hard errors which are very annoying. In the early days, the users may not be able to explore modules due to these false positive errors are my major concerns. https://github.com/llvm/llvm-project/pull/115416 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
