Closed XmiliaH closed 4 years ago
PR #185 should resolve this issue and explicitly throw in places where we don't support getters and setters. Good catch on this behaviour, I was aware that we don't support getters and setters in certain places, but I wasn't aware that this could cause this kind of weird behaviour.
The following code will run the getter even if it is not a getter: