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

Unicode comparison operators parsing differs from ASCII counterparts #6797

Closed
carlobaldassi opened this issue May 9, 2014 · 0 comments · Fixed by #6805
Closed

Unicode comparison operators parsing differs from ASCII counterparts #6797

carlobaldassi opened this issue May 9, 2014 · 0 comments · Fixed by #6805
Labels
domain:docs This change adds or pertains to documentation domain:unicode Related to unicode characters and encodings
Milestone

Comments

@carlobaldassi
Copy link
Member

In particular, they are not parsed as word-boundaries when tokenizing, i.e. they require spaces around them. For example:

julia> a,b = 3,4;

julia> a!=b
true

julia> a≠b
ERROR: a≠b not defined

julia> a>=b
false

julia> a≥b
ERROR: a≥b not defined

julia> a===b
false

julia> a≡b
ERROR: a≡b not defined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:docs This change adds or pertains to documentation domain:unicode Related to unicode characters and encodings
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants