On Sat, Jul 30, 2022 at 01:10:55PM +0200, Giuseppe D'Angelo via Development
wrote:
> On 28/07/2022 22:54, Thiago Macieira wrote:
> > This case can be considered a Category B source incompatible change as per
> > https://quips-qt-io.herokuapp.com/quip-0006.html, because it clearly
> > introduces
Hi,
On 28.07.22 22:54, Thiago Macieira wrote:
This case can be considered a Category B source incompatible change as per
https://quips-qt-io.herokuapp.com/quip-0006.html, because it clearly
introduces ambiguity.
But {} is particularly special, so I don't know how we'd deal with it. I don't
Hi,
On 30/07/2022 14:13, A. Pönitz wrote:
Ultimately, I think that we simply don't "really" deal with this particular
problem, and may accept the SIC. For instance, if we add a QStringView
overload to a function taking QString, this is a SIC but I don't think we
would reject the addition. I
On 28/07/2022 22:54, Thiago Macieira wrote:
This case can be considered a Category B source incompatible change as per
https://quips-qt-io.herokuapp.com/quip-0006.html, because it clearly
introduces ambiguity.
But {} is particularly special, so I don't know how we'd deal with it. I don't
think
On Thursday, 28 July 2022 13:54:48 PDT Thiago Macieira wrote:
> [resent with my subscribed address, which means it won't arrive in
> kde-devel] [cross-posting to Qt dev ML - dunno if it'll arrive because I'm
> subscribed with different addresses]
Link to thread in kde-devel:
[resent with my subscribed address, which means it won't arrive in kde-devel]
[cross-posting to Qt dev ML - dunno if it'll arrive because I'm subscribed
with different addresses]
On Wednesday, 27 July 2022 14:54:55 PDT Friedrich W. H. Kossebau wrote:
> And has no-one else yet run into this
