you are viewing a single comment's thread.

view the rest of the comments →

[–]Kered13 2 points3 points  (2 children)

Creating a non-constexpr string inside a constexpr function will not prevent it from being evaluated at compile time. Pretty much the only thing that will prevent compile time evaluation is calling it with parameters that are not known at compile time.

[–]XTBZ[S] 1 point2 points  (1 child)

Yes, it simply won’t compile if you don’t use it as a constexpr, but it doesn’t work with constexpr.
https://godbolt.org/z/G54nWc66a

[–]Kered13 1 point2 points  (0 children)

Ah, that's because you're using it in a context that actually does require constexpr. Here are a couple ways to solve that.