-
Notifications
You must be signed in to change notification settings - Fork 65
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
Relatively small Unicode wins #290
base: main
Are you sure you want to change the base?
Conversation
We might decide to take some pieces of this, all of it, or continue on to add (perhaps-optional?) support for non-BMP character classes. |
The |
@@ -33,12 +33,15 @@ line | |||
/ buzz | |||
|
|||
fizzbuzz = f:fizz _ b:buzz { return f + b } | |||
fizz = @"fizz"i !{ return currentNumber % 3 } | |||
buzz = @"buzz"i !{ return currentNumber % 5 } | |||
\u0066izz 'fizz' = @"fizz"i !{ return currentNumber % 3 } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly I'd rather ban everything outside of [a-z_]i[a-z0-9_]i
.
cc5094e
to
fa92718
Compare
d9787e0
to
c21d7f6
Compare
…capeSequence is used.
Breaks on this grammar: |
A prototype for dealing with Unicode codepoints above U+FFFF. In JavaScript, you can spell these
\u{1f41d}
(U+1f41d: HONEYBEE 🐝).Added:
"strings"
can use escapes like\u{1f41d}
. For non-BMP characters, these escapes generate two UTF-16 bytes..
now matches full non-BMP characters