Why is a parameter not a constant expression in a constexpr function? [duplicate]

Question

Could you please explain why this code doesn't compile?

// source.cpp
constexpr const char* func(const char* s) { return s;}

constexpr bool find(const char *param) {
   constexpr const char* result = func(param);
   return (param == 0);
}

int main()
{
   constexpr bool result = find("abcde");
}

The compile command:

$ g++ -std=c++14 source.cpp

I've tried gcc5.4 and gcc6.4. The error:

source.cpp: In function ‘constexpr bool find(const char*)’:
source.cpp:5:46: error: ‘param’ is not a constant expression
 constexpr const char* result = func(param);
                                          ^

A string is not an integral value so it cannot be resolved during compilation. This contradicts the constexpr definition of find. See en.cppreference.com/w/cpp/language/constexpr — HappyCactus
– HappyCactus, Commented Jan 29, 2019 at 12:55

StoryTeller - Unslander Monica · Accepted Answer · 2019-01-29 13:03:55Z

15

A function parameter is never a constant expression. Remember that constexpr functions are just like regular functions. They can be called at run-time too. So we cannot assume the address passed in param is to something that is a constant expression, and so cannot use it to initialize a constexpr variable or return value.

You can pass string literals to constexpr functions and produce constexpr results, for instance:

constexpr bool find(const char *param) {
   return (param[0] == 0);
}

int main()
{
   constexpr bool result = find("abcde"); // OK!
}

The function is callable in a constant expression, when given a constant expression. But it cannot assume it is only ever called in a constant expression (I know, one can go cross-eyed thinking about it).

answered Jan 29, 2019 at 13:03

StoryTeller - Unslander Monica

172k22 gold badges401 silver badges481 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

embedc Over a year ago

Your example uses parameter to produce a constant expression, right? My example do the same. What is the difference?

StoryTeller - Unslander Monica Over a year ago

@embedc - The difference is that your example assumes the argument is unconditionally constexpr, mine does not.

Collectives™ on Stack Overflow

Why is a parameter not a constant expression in a constexpr function? [duplicate]

1 Answer 1

2 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Linked

Related