Deprecation warning is misleading, should be changed #2029
Closed
OliverKunc
started this conversation in
Ideas
Replies: 1 comment
-
Could you file it at https://github.com/llvm/llvm-project/issues/ please, with a code example? The warning is produced by the clang frontend*, and clangd just surfaces it over LSP. (* I think; it's hard to be sure without a code example. The other possibility is it's produced by clang-tidy, for which https://github.com/llvm/llvm-project/issues/ is also the right place to report.) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
not sure whether this belongs here, please tell me if there is a better place for this.
When I call a constructor of MyClass and that constructor has a deprecation warning, then clangd prints:
I find this misleading. The class itself is not deprecated.
My suggestion would be to replace it with
or
or something similar.
Beta Was this translation helpful? Give feedback.
All reactions