Cascadia-code: ~= ligature

[seanmars]

Same as [== ligature] #46
The distinction between "=" and "~=" is quite subtle too.

[seanmars]

Cascadia Code:

Fira Code:

[ExE-Boss]

They look distinct enough to me.

[weltkante]

hmm, what language does cascadia target? because some languages do ~= as a variant of == but other languages do ~= as a variant of != (not equals)

Making it look like an equality test makes those languages harder to read, they should be clearly distinguishable from equality tests.

[laperraputs513]

Mm

[laperraputs513]

Mmm

[aaronbell]

@seanmars @weltkante Interesting. For Lua (and related languages), would swapping for a not equals ligature be workable? Like this:

I can certainly include a stylistic set variant that forces the not equals form. It'll require Terminal to build in intelligence to turn on the set when in Lua (and using Cascadia Code). @DHowett-MSFT, what do you think?

[DHowett-MSFT]

We can't exactly guess when Lua's in use in the terminal, so this would be another user-driven choice. :smile:

[seanmars]

I think that consistent behavior is less confusing to the user. 😄

[ExE-Boss]

Well, VS Code could support something like:

"[lua]": {
    "editor.fontStylisticSets": "luaNotEquals"
}

[weltkante]

I think the defaults should be easily distinguishable from other operators and any language specific cases should be opt-in. When you are in a terminal you don't know which language you are showing (for example piping source code file sections to stdout via command line tooling is a common operation for me) and you want to make sure that the user can easily read everything regardless of which language he uses in his files.