-
Notifications
You must be signed in to change notification settings - Fork 56
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
Remove custom __getClass method #298
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Why not use |
That won't work if they're from different realms/contexts, right? |
I guess we could use A simpler way to test this is Same problem with |
I followed what seems to be the most used convention to test for Regex objects. |
OK, classical idiom I suppose. I tend to prefer a simpler idiom that does not involve a function call nor allocate memory. |
Right, but this is in the repl where performance isn't much of a concern. |
I still suggest |
Changed it to |
Ben's objection was that objects created in a different realm would not be instances of the same constructors. This is correct, but we do not have support in repl for different realms at the moment. V8 has a global object |
Any chance |
It goes in the same direction, but with a different approach: different object/function names and semantics |
Since the old one never got anywhere I'd say we shouldn't support it. |
No description provided.