> My instance on having few macros isn't just specific to constexpr.

>

> For 'constexpr' in particular, I do believe it is still too early.

> LWG

> doesn't even know what it wants. Having a new macro everytime that

> LWG

> changes its mind sound overkill.  If the desire is to have a macro

> anyway, then I will repeat the suggestion I made previously:  Have

> just one

> macro for constexpr, call it something, and have its value updated

> for

> new released of the committee draft.

 

Gaby, I don't understand what you're suggesting we should do.

 

Here is the relevant excerpt from N3694:

 

N3471

Constexpr Library Additions: utilities

20.2-20.4

__cpp_lib_constexpr_functions

201210

<utility>

N3469

Constexpr Library Additions: chrono

20.11

<chrono>

N3470

Constexpr Library Additions: containers

23.3

<array>

 

What are your proposed edits, if any?

 

Clark