rnk wrote: > > What I'd like to see is a pull request sent to > > https://github.com/microsoft/stl with some agreement about how to structure > > the ifdefs so we can use intrin0.h when it is available. > > Sounds good I'll do that.
Thanks! > I was thinking I could use `__has_include_next`. If > `__has_include_next(<intrin0.h>)` is true then we know clang is providing its > own `intrin0.h`. > > Another option I had was to preemptively get a PR up to MSVC STL with a > `__clang_major__` check for clang 18 assuming this PR gets in before the > release window. > > A custom name like `intrin_msstl.h` works for me as well. I think we can be flexible, and the important thing is that our solution should work for them. https://github.com/llvm/llvm-project/pull/75711 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
