Am Donnerstag, 28. Juli 2022, 14:38:38 CEST schrieb Friedrich W. H. Kossebau:
> Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira:
> > But {} is particularly special, so I don't know how we'd deal with it. I
> > don't think this has come up for us yet. For one, the mailing list th
On Thursday, 28 July 2022 05:38:38 PDT Friedrich W. H. Kossebau wrote:
> Thanks for the link, interesting (Sidenote: Not sure I agree that there are
> SiCs which are acceptable, I know I got upset a few times by such breakages,
> breaking is breaking after all.)
They're all some level of bad. The
Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira:
> [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 proble
[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 problem? E.g. Qt, anyone seen them
> adding new overloads, what did they do there, i
On Wednesday, 27 July 2022 14:37:20 PDT Friedrich W. H. Kossebau wrote:
> * new overload method (and any further ones) will stay special
> * existing consumer code using {} is not that simple to map by human readers
> as to which overload will be used
> * needs C++17, so needs some additional marku
Am Mittwoch, 27. Juli 2022, 13:51:48 CEST schrieb Friedrich W. H. Kossebau:
> Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra:
> > You could try using SFINAE:
> >
> > ```
> > struct Test {
> >
> > void foo() { }
> > void foo(const std::vector& t) { }
> >
>
(David, somehow your emails do not make it from the mailinglist to my inbox
sadly, no idea yet why. Saw your email by chance on the list web interface,
and tosky forwarded it manually to me, so I can reply now here. So might miss
out more :()
Am Samstag, 23. Juli 2022, 20:26:47 CEST schrieb Dav
Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra:
> On Monday, 25 July 2022 14:22:45 CEST Friedrich W. H. Kossebau wrote:
> > Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo:
> > > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H.
> > > Kossebau:
> > > Add
On Monday, 25 July 2022 14:22:45 CEST Friedrich W. H. Kossebau wrote:
> Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo:
> > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau:
> > Adding such an overload as in your example is source incompatible
> > regardless.
On Mon, Jul 25, 2022 at 2:23 PM Friedrich W. H. Kossebau
wrote:
>
> Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo:
> > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau:
> > Adding such an overload as in your example is source incompatible
> > regardless. Se
Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo:
> Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau:
> Adding such an overload as in your example is source incompatible
> regardless. See also our guidelines.
> https://community.kde.org/Policies/
> Binary_Compa
Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau:
> Hi,
>
> (cc: kde-frameworks-devel for heads-up, please reply to kde-devel only)
Sorry replied wrong first :)
> given a class C with a method foo(A a):
> --- 8< ---
> class C
> {
> public:
> void foo(A a);
> };
> --- 8< ---
Hi,
(cc: kde-frameworks-devel for heads-up, please reply to kde-devel only)
given a class C with a method foo(A a):
--- 8< ---
class C
{
public:
void foo(A a);
};
--- 8< ---
Now you want to add an overload, to serve further use-cases as requested by
API consumers:
--- 8<
13 matches
Mail list logo
