-
-
Notifications
You must be signed in to change notification settings - Fork 9
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 operator support? #6
Comments
I'm not a fan of ligatures myself. By default it will match whatever Typescript (i.e Javascript) supports, which allows for UTF-8 characters in source. I think that's generally a bad idea though, and untypable characters that majority of people can't write is a bad idea. Though there's always cases like ascii (and UTF-8) being a westernized set of characters, particularly English characters. I see that there is a decent Japanese following for Derw, so perhaps someone from a non-Western country will have a need for unicode chars. |
A lot of people still have troubles using |
I also feel it might not be good idea to support Unicode at least when it comes to identifier names. Unicode is full of characters that are almost impossible to tell one from the other. ASCII is not perfect but it's well defined subset at least. |
PureScript, Haskell (with
UnicodeSyntax
extension), Dhall, and Agda all support Unicode for operators (as well as custom infix operators). Users can choose to express themselves however they feel.is just as valid as
Some chose to create alternative
Prelude
s to express even more code on both type and term-levels this way. With tooling likepurescript-tidy
allowing users to specifydata UnicodeOption = UnicodeSource | UnicodeAlways | UnicodeNever
project-wide the preference.Other languages like Gluon and Idris have explicitly stated that they do not want want this support because it can create yak-shaving, scares some users off with questions of: how do I type this ‘fancy’ symbol, and offer two ways to do something instead of one.
As someone in the camp that finds ligatures in programming fonts a bad idea and thinking it’s better if you can express your symbol using Unicode if that's what you mean to show and don't want false positives, I prefer the Unicode side, however I can understand the argument from the other side.
Does derw have a stance on future Unicode support (or defer til later)?
The text was updated successfully, but these errors were encountered: