Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why main can not be a constexpr?

Tags:

When you attempt to use constexpr with main like this:

constexpr int main() 

gcc and clang complain:

error: cannot declare '::main' to be inline

error: 'main' is not allowed to be declared constexpr

Let's see what requirements for constexpr function are:

A constexpr function must satisfy the following requirements:

  • it must not be virtual
  • its return type must be LiteralType
  • each of its parameters must be literal type

What is LiteralType?

A literal type is any of the following

  • void(since c++14)
  • scalar type
  • reference type
  • an array of literal type

What must the function body include?

  • null statements
  • static_assert declarations
  • typedef declarations and alias declarations that do not define classes or enumerations
  • using declarations
  • using directives
  • exactly one return statement that contains only literal values, constexpr variables and functions.

The following examples:

constexpr int main() { ; }  constexpr int main() { return 42; }  constexpr int main() { // main defaults to return 0  } 

seems to fit all these requirements. Also with that, main is special function that runs at start of program before everything else. You can run constexpr functions from main, and in order for something marked constexpr to be constexpr, it must be run in a constexpr context.

So why is main not allowed to be a constexpr?

like image 420
Tory Webster Avatar asked Feb 03 '14 23:02

Tory Webster


People also ask

What can be constexpr?

constexpr indicates that the value, or return value, is constant and, where possible, is computed at compile time. A constexpr integral value can be used wherever a const integer is required, such as in template arguments and array declarations.

Is not usable as a constexpr function?

It means that compiler makes most general assumptions when compiling this function. And this assumption is that arguments are non-compile-time. It means that compiler can't guarantee that your if-constexpr is always compile-time, hence the error about it.

Why does constexpr need to be static?

A static constexpr variable has to be set at compilation, because its lifetime is the the whole program. Without the static keyword, the compiler isn't bound to set the value at compilation, and could decide to set it later.

Does C have constexpr?

No, no such thing exists in C.


2 Answers

No, this is not allowed the draft C++ standard in section 3.6.1 Main function paragraph 3 says:

[...]A program that defines main as deleted or that declares main to be inline, static, or constexpr is ill-formed.[...]

main has to be a run-time function and as Lightness says it makes no sense since you can't optimize main away.

like image 173
Shafik Yaghmour Avatar answered Sep 19 '22 15:09

Shafik Yaghmour


The standard gives the precise signature for main, so the compiler is allowed to reject other signatures. Even more specifically, it prescribes that main cannot be constexpr, static, or some other things.

If you're wondering why, the compiler is allowed to insert code at the beginning of main (to do stuff like initialize global variables, etc.) which could make it non-constexpr (which is why e.g. a program is not allowed to call main explicitly).

like image 30
user3175411 Avatar answered Sep 19 '22 15:09

user3175411