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

Rename undefined to object #90

Closed
71104 opened this issue May 30, 2016 · 3 comments
Closed

Rename undefined to object #90

71104 opened this issue May 30, 2016 · 3 comments

Comments

@71104
Copy link
Owner

71104 commented May 30, 2016

"Everything is an object".

This one deserves release 0.10.0.

@71104
Copy link
Owner Author

71104 commented May 30, 2016

Implement #84 before this one. Removal of LazyValue might actually mean there is no need of an ObjectValue class at all, as AbstractValue would become the root of all values.

@71104
Copy link
Owner Author

71104 commented Jun 4, 2016

This naming is actually sound: given that everything is an object, some objects are classified as booleans, numbers, strings, lists, or lambdas, while others are not classified as any of the previous - they are undefined.

The naming convention will be kept along with the undefined keyword.

@71104 71104 closed this as completed Jun 4, 2016
@71104 71104 added the wontfix label Jun 4, 2016
@71104
Copy link
Owner Author

71104 commented Jun 4, 2016

Also, ObjectValue or UndefinedValue will not be removed in favor of rooting everything to AbstractValue because, unfortunately, we still have to support JavaScript by providing something that marshals to JavaScript undefined or JavaScript null, so those two special values will extend AbstractValue but not UndefinedValue. #94 has been opened to address this.

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

No branches or pull requests

1 participant