| Issue |
153522
|
| Summary |
Need a way to deprecate `__has_feature(X)` with a message to switch to `__has_extension(X)` instead
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
ojhunt
|
We have many "features" that should really be "extensions" but currently we have no way to report that the use of those features should be replaced with `__has_extension` tests instead.
At least a few of these features are low volume/constrained enough that issuing a deprecation warning and a direct devs from using `__has_feature` to `__has_extension` and then eventually removing the `__has_feature` path, or possibly making it an error at some point, something like
1. Add deprecation warning saying to switch from `__has_feature(X)` to `__has_extension(X)`
2. <wait some number of releases>
3. Make `__has_feature(X)` produce an error message rather than a warning
(1) and (2) allow for migration, (3) means that people don't silently have the `__has_feature` tests stop working.
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
