C++17 in PIM

[Volker Krause]

+1, recently hit that constraint once as well. 

C++17 is out since 3 years, and all supported platforms should have compiler 
support by now I think, so using it where it helps us seems sensible.

Regards,
Volker

On Tuesday, 24 March 2020 10:55:21 CET Daniel Vrátil wrote:
> Hi all,
> 
> any objection to using C++17 in KDE PIM?
> 
> I'm not saying we should go and flip the switch in the entire PIM - it makes
> no sense to do so if we don't use any of the language features anywhere. On
> the other hand I think we should not be constraining ourselves to C++11 (or
> even 14) unnecesarily. If one needs a feature from C++17 while fixing a bug
> or implementing a feature, they should just be able to flip the switch in
> the repo. Our codebase contains a lot of legacy (== C++98+auto) code,
> opening doors to modern language features can only benefit us and make PIM
> more attractive for new contributors.
> 
> If there are no objections, I'd like to start by switching Akonadi to C++17
> (because oh boy, I just want my structured bindings! :)
> 
> /Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20200324/3114df4e/attachment-0001.sig>