On 11/26/2013 11:43 AM, Paolo Carlini wrote:
We have got a bunch of testcases, for example constexpr-ex4.C - attached for your convenience - which trigger the assert !really_overloaded_fn (t) ... What do you suggest?
Aha. Well, in that case we really can't get a constant value, so I'd assert allow_non_constant, set *non_constant_p, and return t.
Actually, I'd do that any time we get a function COMPONENT_REF, since that will only ever happen under the checking maybe_constant_value call anyway. So a small expansion of your original patch.
Jason
