From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 991B03858D35; Sat, 18 Nov 2023 18:20:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 991B03858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1700331638; bh=Mu6k2MhyhDqzPKIeEzib/zfBBU2yzd5wi+XTZHT6MnE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=H/vaBBEE9hvUjqRVVmHIeXGqvvj1ZMQpJFcfFk3XvWBPgPMLQ2NC59GhgDLaXmqeR 3zCnhx5z8zYDjfRLJ/wRmg9Fh1yAd27iPWIkqCy/zPv2phTwaZJgtIL10QcHthr5Rc I0yVKxtNG5G662iTZS3b4I+Ets6NQRzMsiFSuaEY= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112607] : _Normalize does not consider char_type for the basic_string_view case Date: Sat, 18 Nov 2023 18:20:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112607 --- Comment #3 from Jonathan Wakely --- The standard tries quite hard to avoid this kind of specialization: https://eel.is/c++draft/format.formatter.spec#note-1 But I suppose you can contrive this kind of custom formatter, or the invers= e, i.e. std::formatter, wchar_t>=