-
Notifications
You must be signed in to change notification settings - Fork 16
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
language design questions #21
Comments
delete is not the same as setting to nil. This is not lua. Candor allows having properties that point to nil. This makes JSON interop much easier for example. As far as type coercion, I agree, == and != should be the same as JS === and !==. |
will candor distinguish between |
I believe so yes. If not, it should. I know I asked for this with "new" and I assume the logic is the same for all keywords. |
hmm. i saw no |
right, "new" was renamed to "clone". But it was "new" when I had @indutny make sure it could be used for other stuff. |
Please, consider answering some naive ones:
==
,!=
. they are known as source of subtle bugs in JS, and every tutorial i read said i should use===
,!==
instead.delete foo[bar]
can be replaced withfoo[bar] = nil
, which frees rather useful keyword and can internally behave equally.+
, which is known to be another source of subtle bugs.TIA,
--Vladimir
The text was updated successfully, but these errors were encountered: