zmodem wrote: Thanks Aaron, that's a good example.
This is a pickle; it doesn't seem like there's an obviously Right Solution(tm) here. I think we're agreeing on the first part, that unhandled deprecated enums should trigger the "not covered" warning. Some users will prefer to handle that with a `default:` to avoid using the deprecated enum, while others will want to handle the enum explicitly and suppress the warning. Corentin's flag suggestion seems like the best way to satisfy both camps. I've updated the PR. https://github.com/llvm/llvm-project/pull/138562 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
