On Friday 7 June 2024 08:40:33 GMT-7 Ivan Solovev via Development wrote:
> IIUC, the problem of extra allocations is covered by the transcoding
> iterators and views in the paper that was linked by Giuseppe.
Yes and no.
That appears to transfer the responsibility of transcoding to the formatter,
> Tomorrow, who knows -- thus my concern that we need to be aligned with
> upstream, or we risk divergence. Cf. for example this approach:
>
>> https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2728r6.html#add-utf_view-specialization-of-formatter
Thanks for the link. If the paper gets acce
On Friday 7 June 2024 01:53:55 GMT-7 Ivan Solovev via Development wrote:
> Note that currently the standard does not allow to mix char and wide char
> strings, so something like this will not work:
>
> std::wstring wstr = ~~~;
> std::format("{}", wstr); // ERROR!
>
> That would mean the followi
>
> On 4 Jun 2024, at 09:29, Jani Heikkinen via Development
> wrote:
>
> Hi!
> Qt 6.8 API Change Review is started, see
> https://bugreports.qt.io/browse/QTBUG-125859
> generated diffs are here:
> • https://codereview.qt-project.org/q/topic:api-change-review-6.8
> • https://codereview
On 07/06/2024 10:53, Ivan Solovev via Development wrote:
Hi
> I think we should conceptually separate formatting from printing on a
> terminal. std::format isn't /_just_/ for printing on terminals
I agree. But the same question about encoding to be used is still valid
here.
> What do you
Peppe had said:
>> I'm not following this. If I do
>>
>> std::format("{} {}", utf8string, latin1string)
>>
>> what am I supposed to get out? A string which is a mix of two different
>> encodings? I don't think that's ever possibly wanted.
Ivan Solovev (7 June 2024 10:53) replied:
> Yes, that's ex
Hi
> I think we should conceptually separate formatting from printing on a
> terminal. std::format isn't _just_ for printing on terminals
I agree. But the same question about encoding to be used is still valid here.
> What do you mean by "readable" here?
I was mostly thinking about "readable in
