Is there a prize for the person who gets the 100th feature macro approved?
On 8/3/2018 3:52 PM, Richard Smith wrote:
We'll presumably need both a language component and a library
component, but user code will only want to test one macro.
Perhaps the compiler should define a macro for language support and
the library should only define its macro if the compiler macro is
defined (as min(compiler macro value, library value)?).
On Fri, 3 Aug 2018, 11:45 Ville Voutilainen,
<ville.voutilai...@gmail.com <mailto:ville.voutilai...@gmail.com>> wrote:
On 3 August 2018 at 21:23, Chris Kennelly <ckenne...@google.com
<mailto:ckenne...@google.com>> wrote:
> P0722, adopted at Rapperswil, added destroying operator delete.
Would it be
> possible to provide a feature test macro for its availability?
..presumably so that you can declare such an operator only if the
macro is defined, so as to
avoid otherwise ill-formed code because std::destroying_delete_t
wouldn't be available?
Makes sense to me.
_______________________________________________
Features mailing list
Features@isocpp.open-std.org <mailto:Features@isocpp.open-std.org>
http://www.open-std.org/mailman/listinfo/features
_______________________________________________
Features mailing list
Features@isocpp.open-std.org
http://www.open-std.org/mailman/listinfo/features
_______________________________________________
Features mailing list
Features@isocpp.open-std.org
http://www.open-std.org/mailman/listinfo/features
