On Tuesday 11 June 2024 13:03:11 GMT-7 Volker Hilsheimer via Development 
wrote:
> Also, if the character value is outside the US-ASCII range, then the only
> alternative would be to interpret it as an incomplete UTF-8 sequence, which
> can’t be the right answer. QString::arg(char) (or operator+(char), for that
> matter) is not usable as a tool to assembly a valid string from individual
> UTF-8 code points, after all.

I dispute the conclusion that we can use the API for an alternate purpose 
because its primary purpose is probably not what the user meant to do.

Ideally, we'd warn them by making the code fail to compile if they used it 
wrongly in the first place.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Principal Engineer - Intel DCAI Fleet Systems Engineering

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to