On May 4, 2021, at 12:33 PM, Charlie Black
mailto:cbl...@vmware.com>> wrote:
Another viewpoint is this is a library and that library can be used by older
applications. So being cutting edge on the complier on the library does not
increase the adoption of Geode.
The public API can’t change
.
Thanks,
Mario.
From: Charlie Black
Sent: Tuesday, May 4, 2021 9:33 PM
To: dev@geode.apache.org
Subject: Re: DISCUSSION: Geode Native C++ 17 adoption
Another viewpoint is this is a library and that library can be used by older
applications. So being cutting edge
: Tuesday, May 4, 2021 at 11:29 AM
To: dev@geode.apache.org
Subject: Re: DISCUSSION: Geode Native C++ 17 adoption
Hi,
Here come my two cents.
To me, upgrading to C++17 is a no brainer given that C++11 is quite old and
C++17 has lots of new features, performance improvements and bug fixes.
The only
Native C++ 17 adoption
Hi everyone,
Sorry for the previous email, I did send it before finishing it by mistake.
Currently Geode Native uses C++11 standard. It has been quite some time since
the standard was released and as of today the latest standard is C++20.
As part of another discussion
Hi everyone,
Sorry for the previous email, I did send it before finishing it by mistake.
Currently Geode Native uses C++11 standard. It has been quite some time since
the standard was released and as of today the latest standard is C++20.
As part of another discussion, some users in the
