Well, I overlooked that.
The solution is to address LWG2453 incidentally. Although <initializer_list> is freestanding, all entities in <iterator> except stream iterators are freestanding after P1642R10, so there is no problem to solve it.
I'd like someone to help me write a proposal because I'm not very good at writing these kinds of standard documents and my English is not very good. I will be very grateful.

On Tue, Aug 30, 2022 at 10:12 PM Giuseppe D'Angelo via Std-Proposals <std-proposals@lists.isocpp.org> wrote:
Hi,

On 30/08/2022 15:43, hamburger blacktea via Std-Proposals wrote:
>
>
> I tried submitting it as a standard library issue, but the LWG chair
> said it needed a proposal. Can someone help?


Please see https://isocpp.org/std/submit-a-proposal

You basically have to produce a document and submit it.

Please read some existing proposal to see what's the expected design of
such a document:

> https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/


As a minimum you have to argue as of why do you think that this removal
makes sense. Just saying, we're 11 years into the making, and so that
removal will break code:

void f(std::initializer_list<int> i) {
   begin(i); // right now works; doesn't after your proposal?
}

So you'd have to justify why this code "deserves to be broken", which is
already a pretty high bar.


HTH,
--
Giuseppe D'Angelo | giuseppe.dangelo@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
--
Std-Proposals mailing list
Std-Proposals@lists.isocpp.org
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals