[KSP2] Property setter parameter name becomes `value` about ksp

[ting-yuan]

Per discussion offline, let's

1. check whether there's anything in the language spec, and
2. align the naming for source and libs.

[neetopia]

does this impact any of your use cases? I think the name itself is not well defined in spec, therefore this is an either way works case, let me know if you have code that directly depends on the name of this setter parameter.

[kuanyingchou]

Ah, in XProcessing we keep the parameter name user defined and change it to "p0" if we see "<set-?>" as it's not valid in source. With this change this logic doesn't work anymore because we don't know if "value" is user-defined or not. Or is there other ways to tell?

[neetopia]

you can check on the origin of the KSValueParameter of the property setter, I got the following output from your repro, does this help?

SYNTHETIC
KOTLIN_LIB

[kuanyingchou]

Yes, checking the origin as well as consistent names both work for us. Thanks!