You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting Unicode in Tact grammar with security and IDE support in mind is not the task we want to spend any time on. There is not that many use cases for Unicode in contracts in first place. Worse, JS doesn't have a native UTF-8/16 support, and even ohm.js doesn't correctly handle surrogate pairs.
Goal:
ban Unicode characters everywhere in grammar
but allow it in strings and comments
but even in strings and comments ban all the characters that can change code layout: all line breaks except \n, and all RTL/LTR characters
Supporting Unicode in Tact grammar with security and IDE support in mind is not the task we want to spend any time on. There is not that many use cases for Unicode in contracts in first place. Worse, JS doesn't have a native UTF-8/16 support, and even ohm.js doesn't correctly handle surrogate pairs.
Goal:
\n
, and all RTL/LTR charactersFor reference: there is also the UNICODE SOURCE CODE HANDLING technical standard: https://www.unicode.org/reports/tr55.
The text was updated successfully, but these errors were encountered: