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

question: will you be re-introducing <class>.name? #302

Open
tony-kerz opened this issue Mar 20, 2014 · 5 comments
Open

question: will you be re-introducing <class>.name? #302

tony-kerz opened this issue Mar 20, 2014 · 5 comments

Comments

@tony-kerz
Copy link

tony-kerz commented Mar 20, 2014

reference:
jashkenas/coffeescript#2052

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2268292-question-will-you-be-re-introducing-class-name?utm_campaign=plugin&utm_content=tracker%2F33145&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F33145&utm_medium=issues&utm_source=github).
@vendethiel
Copy link
Contributor

No, this is a non-writable property

@tony-kerz
Copy link
Author

ok, how about any way to retrieve the class name of an instance?

@vendethiel
Copy link
Contributor

Add a propertyName

@drarmstr
Copy link

drarmstr commented Feb 4, 2015

Adding __name__ to the constructor, just like __super__, would be great for building class hierarchies. Currently, these issue all say to just create our own property in the instance or prototype. Yes, that works, but it becomes tedious and isn't DRY, and so more prone to errors.

@aurium
Copy link

aurium commented Mar 4, 2015

+1 @drarmstr

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

No branches or pull requests

4 participants