llvm/llvm-project

[Clang] Explain satisfaction failure for more type traits

Open

#141,911 opened on May 29, 2025

View on GitHubContributor guide
 (20 comments) (0 reactions) (0 assignees)C++ (10,782 forks)batch import
clang:diagnosticsclang:frontendgood first issue

Repository metrics

Stars
 (26,378 stars)
PR merge metrics
 (PR metrics pending)

Description

Last week, we added the scaffolding for clang to explain why a standard type trait is not satisfied - when used either in a static_assert or as atomic constraint, in Sema::DiagnoseTypeTraitDetails (#141238)

https://gcc.godbolt.org/z/xb7PcxzTx

So far, this has only been done for std::is_trivially_relocatable.

There are plenty of type traits that could benefit from additional diagnostics https://eel.is/c++draft/type.traits#meta.type.synop

I figure adding support for more type traits (one at a time!) could be a good first issue, and it's always nice to improve our diagnostics.

Contributor guide

Research direction
Start by examining the existing implementation for std::is trivially relocatable in Sema::DiagnoseTypeTraitDetails, then pick a type trait from the standard list and add similar diagnostics.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75