https://github.com/nehaGautam07 created https://github.com/llvm/llvm-project/pull/218758
Fixes #143719 `[[clang::no_specializations]]` diagnoses both explicit specializations and partial specializations. The old wording, "explicitly specialized", is ambiguous because that term means only `template <>` specializations in the C++ standard. This uses the wording agreed in #143839. >From fff541267ded6e3bf8e2fe570a7613ca0a92e09c Mon Sep 17 00:00:00 2001 From: neharaj <[email protected]> Date: Tue, 25 Aug 2026 19:33:28 +0000 Subject: [PATCH] [Clang][Docs] Clarify no_specializations wording Fixes #143719 --- clang/include/clang/Basic/AttrDocs.td | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/clang/include/clang/Basic/AttrDocs.td b/clang/include/clang/Basic/AttrDocs.td index 5ec2a68bc038b..95e27ad9a47c4 100644 --- a/clang/include/clang/Basic/AttrDocs.td +++ b/clang/include/clang/Basic/AttrDocs.td @@ -1466,8 +1466,8 @@ Query for this feature with `__has_attribute(diagnose_if)`. def NoSpecializationsDocs : Documentation { let Category = DocCatDecl; let Content = [{ -`[[clang::no_specializations]]` can be applied to function, class, or variable -templates which should not be explicitly specialized by users. This is primarily +``[[clang::no_specializations]]`` can be applied to function, class, or variable +templates for which neither an explicit specialization nor a partial specialization should be declared by users. This is primarily used to diagnose user specializations of standard library type traits. }]; } _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
