I actually find this a little irksome with spago
having git diffs because the formatter’s default is unicode and running spago upgrade-set
doesn’t follow the default and I do a manual change later. Without passing a spago --use-unicode upgrade
flag and having a fork in all projects consuming Dhall, is there any interest in seeing some sort of rc file read on what the user or project prefers as their default so your team can be on the same page?
I agree with all the above arguments on approachability and personally found the unicode support a shiny, cool thing that made me more likely to use the language. I like that Gabriel said indefinite support. It reminds me of Sass: I always loved and preferred the indented syntax, but the SCSS syntax won out because of approachability and similarity with CSS; and as such the tooling chose SCSS to be the default shown, but the support of Sass’s indented syntax was slated to be supported indefinitely (though I moved to SugarSS for different reasons later).