A modern programming language that makes developers happier.

kotlinlang

the issue here is the name `list`. `x`, `y`, or `foo` would be equally informative….

that's an issue, but not _the_ issue, plus this is an example, I also name my example variables like this when showing code for illustration.
And it's not _the_ issue because with `attendeeNames: List&lt;String` it would've been the same, when both fun param and member property have the same name.

exactly - either don’t name them the same or use `this` . if you’re at the bottom of your function and forgot that you local is called the same as your field, your function is too long.
could be e.g. `newAttendees` or `replacement` or something

my point is that naming beats syntax highlighting :slightly_smiling_face:

…and using the `field` reference in setters should be mandatory