https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120390
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2025-05-21
Ever confirmed|0 |1
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=117294
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The error is telling you that the assertion "type is destructible" failed. Like
when you get static_assert(some_cond) or assert(some_cond) and it says that
some_cond failed.
But I usually try to phrase the static assert messages as "X must be Y" to
avoid this ambiguity. I'll change that one.
I don't think this is a compiler bug. The code failed to compile because of a
static_assert, and that's exactly what the compiler tells you. Maybe something
like Bug 117294 could help, if that was extended to static_assert as well as
concept satisfaction failures.