Re: [PATCH] c++: Substitute into function parms in lexical order [PR96560]

2021-06-11 Thread Jason Merrill via Gcc-patches
until they're actually needed. Would that be something to look into as a followup patch? I think the language currently specifies that they're substituted immediately, so probably not unless that changes. -- >8 -- Subject: [PATCH] c++: Substitute into function par

Re: [PATCH] c++: Substitute into function parms in lexical order [PR96560]

2021-06-11 Thread Patrick Palka via Gcc-patches
es, as in the below. > Bootstrapped and regtested on x86_64-pc-linux-gnu. Ping > > BTW, now that LAMBDA_EXPR has LAMBDA_EXPR_REGEN_INFO I think we have > enough information to defer substituting into lambda default arguments > until they're actually needed. Would that be someth

Re: [PATCH] c++: Substitute into function parms in lexical order [PR96560]

2021-04-29 Thread Patrick Palka via Gcc-patches
uting into lambda default arguments until they're actually needed. Would that be something to look into as a followup patch? -- >8 -- Subject: [PATCH] c++: Substitute into function parms in lexical order [PR96560] This makes tsubst_arg_types substitute into a function's parameter ty

Re: [PATCH] c++: Substitute into function parms in lexical order [PR96560]

2021-04-28 Thread Jason Merrill via Gcc-patches
On 4/28/21 2:24 PM, Patrick Palka wrote: This makes tsubst_arg_types substitute into a function's parameter types in left-to-right order instead of right-to-left order, in accordance with DR 1227. Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk? [ diff generated w

[PATCH] c++: Substitute into function parms in lexical order [PR96560]

2021-04-28 Thread Patrick Palka via Gcc-patches
This makes tsubst_arg_types substitute into a function's parameter types in left-to-right order instead of right-to-left order, in accordance with DR 1227. Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk? [ diff generated with -w to hide noisy whitespace changes ]