-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infinite recursion when trying to access an uninitialized property with getter function #403
Comments
This seems like a bug to me. |
One solution might be to stop filtering out dynamic properties from the constructor args. I.e., remove this line (and update tests to match) Line 51 in ffb8ca9
The object constructor would then have signature This intersects with #376, where we are also discussing changing the object constructor signature. |
The current design of property getting is confusing to me. It seems to require that a property with a getter not use its underlying attribute value at all. The getter is run if and only if the attribute value is I would prefer that instead we always run the getter, if present, and we use the same trick as property setting to avoid infinite recursion (as already proposed in the C code). |
When trying to access an uninitialized property that has a getter, a stack overflow occurs
as soon as I set a value the code works. Is this behaviour ok?
default property value also does not help.
The text was updated successfully, but these errors were encountered: