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

Make binary/octal literal example less confusing #29

Merged
merged 1 commit into from
Mar 5, 2014
Merged

Make binary/octal literal example less confusing #29

merged 1 commit into from
Mar 5, 2014

Conversation

mathiasbynens
Copy link
Contributor

0b111110111 === 0o767 === 503 === 0x1F7 might not be the best example to demonstrate these features. The intention might be clear, but in JavaScript this statement evaluates to false (just like 1 === 1 === 1 === 1 would). Let’s avoid the confusion.

`0b111110111 === 0o767 === 503 === 0x1F7` might not be the best example to demonstrate these features. The intention might be clear, but in JavaScript this statement evaluates to `false`. Let’s avoid the confusion.
@mathiasbynens
Copy link
Contributor Author

Ah, my text editor cleaned up trailing whitespace. See https://github.com/lukehoban/es6features/pull/29/files?w=1 for the whitespace-free diff.

@lukehoban
Copy link
Owner

Looks good - and trailing whitespace cleanup is a bonus.

lukehoban added a commit that referenced this pull request Mar 5, 2014
Make binary/octal literal example less confusing
@lukehoban lukehoban merged commit cb3cf67 into lukehoban:master Mar 5, 2014
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