JDevlieghere added a comment. As discussed offline, I think it's impossible to enforce the semantic difference between the two and we'll inevitable end up with the `LLDB_UNSUPPORTED` used where `LLDB_DEPRECATED` should be used but someone didn't know, or worse someone decides to add a third macro to mean something slightly different. My suggestion was to have the two macros be named the same modulo a prefix to indicate whether there's a message or not (for example `LLDB_DEPRECATED_FIX` or `LLDB_DEPRECATED_FIXIT` and `LLDB_DEPRECATED` if there's not).
Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D153928/new/ https://reviews.llvm.org/D153928 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
