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
The issue is if you have ligatures turned on and "ss10" set then >= looks odd next to the ?. And since ReScript has its own formatter which strips any whitespace between the = and ? there isn't a way to avoid it without turning off "ss10" or ligatures entirely. So if there's a way to disable ligatures when the pattern >=? is found then that would be great to avoid this character sequence clash.
The text was updated successfully, but these errors were encountered:
That makes sense. We should take a look at it. BTW I'm a big fan of the ReScript and been co-organizing the first ever two conferences for it here in Vienna.
What feature are you proposing?
In the ReScript programming language, having a parameter that consists of the characters
>=?
can happen when you have a typed parameter that takes a type variant that is optional. You can see an example at https://rescript-lang.org/docs/manual/latest/function#signatures-and-type-annotations of the line(~color: color, ~radius: option<int>=?) => {
.The issue is if you have ligatures turned on and "ss10" set then
>=
looks odd next to the?
. And since ReScript has its own formatter which strips any whitespace between the=
and?
there isn't a way to avoid it without turning off "ss10" or ligatures entirely. So if there's a way to disable ligatures when the pattern>=?
is found then that would be great to avoid this character sequence clash.The text was updated successfully, but these errors were encountered: