cor3ntin added a comment. In D156247#4534645 <https://reviews.llvm.org/D156247#4534645>, @ilya-biryukov wrote:
> At Google, we would like to postpone adoption of coroutines until the > aforementioned bugs are fixed, but we feel that Clang 17 would be a good > candidate to enable other C++20 features (sans Modules). > We could have landed a local patch with a similar warning in our main > toolchain that we control tightly. However, we want to have it for other > toolchains (e.g. Apple Clang) that are based on upstream and we do not > control. Given that adoption by Apple Clang is one of the motivation to make this change upstream, do we have a reasonable expectation they would pick this change soon? Historically Apple follows a release schedule that is not synchronized with the LLVM release process. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D156247/new/ https://reviews.llvm.org/D156247 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
