Re: [C++PATCH] [PR87322] move cp_evaluated up to tsubst all lambda parms

2019-02-08 Thread Jason Merrill
On 2/8/19 1:58 AM, Alexandre Oliva wrote: On Feb 7, 2019, Jason Merrill wrote: + PR c++/86322. */ Wrong PR number. Thanks + if (local_specializations) +if (tree r = retrieve_local_specialization (t)) + return r; Hmm, I would expect this to do the wrong thing for pack

Re: [C++PATCH] [PR87322] move cp_evaluated up to tsubst all lambda parms

2019-02-07 Thread Alexandre Oliva
On Feb 7, 2019, Jason Merrill wrote: >> + PR c++/86322. */ > Wrong PR number. Thanks >> + if (local_specializations) >> +if (tree r = retrieve_local_specialization (t)) >> + return r; > Hmm, I would expect this to do the wrong thing for pack expansion of a > lambda, giving us

Re: [C++PATCH] [PR87322] move cp_evaluated up to tsubst all lambda parms

2019-02-07 Thread Jason Merrill
On 2/7/19 2:24 AM, Alexandre Oliva wrote: From: Alexandre Oliva A lambda capture variable initialized with a lambda expr taking more than one parameter got us confused. The first problem was that the parameter list was cut short during tsubsting because we tsubsted it with cp_unevaluated_oper

[C++PATCH] [PR87322] move cp_evaluated up to tsubst all lambda parms

2019-02-06 Thread Alexandre Oliva
From: Alexandre Oliva A lambda capture variable initialized with a lambda expr taking more than one parameter got us confused. The first problem was that the parameter list was cut short during tsubsting because we tsubsted it with cp_unevaluated_operand. We reset it right after, to tsubst th