Fix #10285: Fix scheme for handling setter names #10584
Conversation
|
This is a WIP that needs help to be pushed over the finish line. I addressed the immediate problem with confusion between setters and unique names in this commit. The idea is to create a semantic setter name that composes correctly with the other names. But now the task is to use this to simulate Scala-2's handling of getters, setters and fields for this. And I just can't make sense of it, even after studying Scala-2 generated code at some length of time. So, I propose @sjrd to take this up again. If you have questions how semantic names work I am happy to answer them. But I believe the current problems lie with understanding what exactly Scala 2 does here (at least for me that seems to be the case). EDIT: I think I got it to work. Let's see what the CI says. |
…ived names Adding "_=" to the last part of a name does not work if that name is a unique name or other derived name, since the resulting name would print like `x_=$1` instead of `x$1_=`. Use a new semantic name for synthetic setter suffix instead.
3 participants
No description provided.