Re: C++17

2018-07-10 Thread Kjell Ahlstedt via gtkmm-list
On 14 April 2018 at 15:38, Murray Cumming wrote: What are you using from C++17? Nothing major. Just some constexpr if, std::apply() and std::invoke(): https://github.com/libsigcplusplus/libsigcplusplus/commits/master GCC's C++17 implementation is not stable yet, so there

Re: C++17

2018-04-14 Thread Jonathan Wakely
On 14 April 2018 at 15:38, Murray Cumming wrote: > On Thu, 2018-04-12 at 21:10 +0100, Jonathan Wakely wrote: >> On 12 April 2018 at 21:02, Murray Cumming wrote: >> > I've just released a version of libsigc++-3.0 (currently unstable) >> > that >> > requires C++17. This means that gtkmm-4.0

Re: C++17

2018-04-14 Thread Murray Cumming
On Thu, 2018-04-12 at 21:10 +0100, Jonathan Wakely wrote: > On 12 April 2018 at 21:02, Murray Cumming wrote: > > I've just released a version of libsigc++-3.0 (currently unstable) > > that > > requires C++17. This means that gtkmm-4.0 (currently unstable) > > requires > > C++17 too. I should have

Re: C++17

2018-04-12 Thread Jonathan Wakely
On 12 April 2018 at 21:02, Murray Cumming wrote: > I've just released a version of libsigc++-3.0 (currently unstable) that > requires C++17. This means that gtkmm-4.0 (currently unstable) requires > C++17 too. I should have mentioned it first, but I think this is fine. What are you using from

Re: C++17's string_view (was Re: Making use of move semantics?)

2017-06-13 Thread Jonathan Wakely
On 13 June 2017 at 08:31, Murray Cumming wrote: > > So, I think: > 1. We would use std::string_view everywhere if all the C functions took > a length instead of assuming null-termination. That's not going to > happen. > > 2. Overriding all methods to take either a const char* or a std::string >