News for hackers. Stuff that matters.
Re:Dev Fonts by Measter on Friday November 20, 2020 @07:37AM (#25159843)
Of course. A `==` is two characters long, while `===` is three characters long. Also, with the font I use (Fire Code) the `===` ligature has three lines, making it even easier to distinguish.
Re:Dev Fonts by BrandoElFollito on Friday November 20, 2020 @07:43AM (#25159883)
I just had a look at Fire Code. How do you distinguish -> with ligatures from → (an Unicode arrow)?
Re:Dev Fonts by matthewmacleod on Friday November 20, 2020 @08:10AM (#25160101)
Personally, it’s never really come up. I have no Unicode arrows in my actual source code.

On the occasion it’s in a string literal or whatever the it’s pretty obviously different, because it’s a single-width character as opposed to the double-width ligature.

Re:Dev Fonts by d3nj4l on Friday November 20, 2020 @07:47AM (#25159928)
The ligaturized -> is two characters wide and is pretty easy to tell apart.
Re:Dev Fonts by kps on Friday November 20, 2020 @09:31AM (#25160729)
So it looks like U+27F6 ⟶ rather than U+2192 →?
Re:Dev Fonts by saurik on Friday November 20, 2020 @09:53AM (#25160957)
Sure, but in a monospaced font both of those arrows would have to fit into the same small box, so 27F6 might be the full width while 2192 would be some partial width, while a -> ligature would be two widths.
Re:Dev Fonts by quarantine on Friday November 20, 2020 @08:00AM (#25160009)
The Unicode arrow looks smaller and is positioned lower, while the ligature has the same size as -> with the dash extended into the 'arrow'. Not that I use this frequently.
Re:Dev Fonts by speedgoose on Friday November 20, 2020 @12:56PM (#25162985)
The Unicode arrow is most likely throwing an error in the linter or compiler and is underlined with a red line.