| ▲ | coldtea 4 hours ago | |||||||
The above is a very thick response that doesn't address the parent's points, just sweeps them under the rag with "that's just how it was designed/it works". "Did you miss the part where I explained to you there's no way to identify that it's a member variable?" No, you you did miss the case where that in itself can be considered nuts - or at least an unfortunate early decision. "this just how things are dunn around diz here parts" is not an argument. | ||||||||
| ▲ | 1718627440 3 hours ago | parent | next [-] | |||||||
> No, you you did miss the case where that in itself can be considered nuts - or at least an unfortunate early decision. This is not a side implementation detail, that they got wrong, this is a fundamental design goal of Python. You can find that nuts, but then just don't use Python, because that is (one of) that things, that make Python Python. | ||||||||
| ▲ | mathisfun123 3 hours ago | parent | prev [-] | |||||||
> considered nuts - or at least an unfortunate early decision Please explain to us then how exactly you would infer a variable with an arbitrary name is actually a reference to the class instance in an interpreted language. | ||||||||
| ||||||||