Switching to C++14?

[offa]

What about switching to C++14 (eg. in form the of seasocks v1.4)?

C++14 is now widely adopted and supported. Furthermore, GCC uses it as default since GCC6 and Clang will also do so from Clang6 onwards. Pretty much every OS should have at least GCC5 (respectively capable Clang) somehow available too.

---

Todo

• [x] Enable C++14 on master
• [x] Tag and release current HEAD as v1.3.2
• [x] Add a note, that v1.4.x will require C++14
• [x] Review supported compiler

[mattgodbolt]

Absolutely. I see no reason not to...though I know one user internal to the company I work for is stuck on an old GCC. I'm happy to move forward (C++17 is now ratified!), and leave them on v1.3 for now. Feel free to upgrade, or I'll look in to when I have time.

On Fri, Sep 8, 2017 at 10:29 AM offa notifications@github.com wrote:

What about switching to C++14 (eg. in form the of seasocks v1.4)?

C++14 is now widely adopted and supported. Furthermore, GCC uses it as default since GCC6 and Clang will also do so from Clang6 onwards. Pretty much every OS should have at least GCC5 (respectively capable Clang) somehow available too.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mattgodbolt/seasocks/issues/79, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmsdXb3yigDdIQL_Qyvka9ICerI7cgtks5sgV1YgaJpZM4PRVtW .

[offa]

Perfect! So I'll create a release of the current Head as v1.3.2 and upgrade master to C++14.

[offa]

That's it! Just one thing I can't to: Updating the Topics and replace cpp11 with cpp14.

[mattgodbolt]

Topics updated! Thanks so much!