larsenwork
Ambiguity of things like <=
It seems that Monoid has a ligature for <= and probably other ambiguous cases as well. Hasklig didn't want to add <= (see i-tu/Hasklig#21) because some languages (in certain contexts) use it to mean something else than less-than-or-equal. So, when I use Monoid and see the ligature for less-than-or-equal, in some places it's actually the wrong thing to display. Has this issue been considered before adding ligatures for cases like <=?
I'd like to add that in Haskell, the <= and >= ligatures make Kleisli composition (>=>, <=<) look pretty funky.
May be the right approach is to add ligatures for ">=>" and "<=<" that will undo the "<=" and ">=" ligatures?
@tuncer is has been considered but basically I don't code in any language where <= doesn't mean "less than or equal to" so that's why it's there. Not sure what to recommend other than using non ligature version for this. @luben that should be easily doable - thanks for the suggestion.
The only other plaint for my Haskell (or F#) is <<< \ >>>. Such a lovely font 🙏
@AppShipIt ¸ I use >>> and <<< operators in Scala, what is the problem you see with them?
I suppose it's not a bug. As of December there's just no ligature defined (as opposed to << / >>)? I mentioned it because in Haskell the operators are related.
This doesn't seem to be fixable without "advanced" OpenType features or generating language-specific variants of the typeface. Therefore, I think the ticket can be closed.