Skip to content

Correct class naming for the inspector - #33

Open
nnseva wants to merge 2 commits into
jneen:masterfrom
nnseva:master
Open

Correct class naming for the inspector#33
nnseva wants to merge 2 commits into
jneen:masterfrom
nnseva:master

Conversation

@nnseva

@nnseva nnseva commented Jan 4, 2015

Copy link
Copy Markdown

Doing trick like proposed we are passing correct names to the inspector.

What is not good, I don't know how to check inspector behaviour correctly. Really I've checked it in the browser manually, so you might wish to improve the testcases.

@jneen

jneen commented Jan 4, 2015

Copy link
Copy Markdown
Owner

This seems intriguing. I'd like to see some performance numbers on it though, since it introduces a string eval, and I'm not sure how that plays with VMs

@nnseva

nnseva commented Jan 9, 2015

Copy link
Copy Markdown
Author

The string eval may take some performance penalty, but I think it should not affect the production code noticable in this case, because this penalty will aply only to class (metaclass object) creation code, while the instance creation code should not be affected.

@jneen

jneen commented Jan 9, 2015

Copy link
Copy Markdown
Owner

I believe that's true too, but I would like to see it tested and verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants