Skip to content
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

Check the effects of become: in class and object proxies #9

Open
guillep opened this issue Feb 15, 2017 · 0 comments
Open

Check the effects of become: in class and object proxies #9

guillep opened this issue Feb 15, 2017 · 0 comments
Labels

Comments

@guillep
Copy link
Owner

guillep commented Feb 15, 2017

Probably become is now well supported by current implementation.

Becoming an object by it's proxy should not create much extra problems.
However, doing it with classes will probably break everything as objects will break the lookup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant