https://github.com/tonsky/FiraCode/blob/master/README.md
https://www.reddit.com/r/programming/comments/4zsr4y/monospaced_font_with_programming_ligatures_in/

It doesn't looks bad with D, even if I'm not a big fan of the && and @.

Am Sun, 28 Aug 2016 06:17:53 +0000
schrieb Basile B. <b2.temp@gmx.com>:

> https://github.com/tonsky/FiraCode/blob/master/README.md https://www.reddit.com/r/programming/comments/4zsr4y/monospaced_font_with_programming_ligatures_in/
> 
> It doesn't looks bad with D, even if I'm not a big fan of the && and @.

Nice find. I didn't know you could do this. Unfortunately it doesn't render ℕ and following characters at the same width, because I use that a lot.

-- 
Marco

On Sunday, 28 August 2016 at 06:17:53 UTC, Basile B. wrote:
> https://github.com/tonsky/FiraCode/blob/master/README.md
> https://www.reddit.com/r/programming/comments/4zsr4y/monospaced_font_with_programming_ligatures_in/
>
> It doesn't looks bad with D, even if I'm not a big fan of the && and @.

Bad things are waiting for you to forget a space:

x<-y        (x less-than (negate y)) becomes (x back-arrow y)
x<*ptr      (x less-than (dereference ptr)) becomes (x very-haskell-op ptr)


Even worse if you use C++:

MyStrangeTemplate<-5> x;      becomes ((MyStrangeTemplate back-arrow 5) greater-than x)


Some things are clearly designed for markup and functional-style languages and don't look that good on C-style ones. But apart from that, it is well-made. I may use it, but probably not for D.

On Sunday, 25 September 2016 at 09:39:56 UTC, Lodovico Giaretta wrote:
> On Sunday, 28 August 2016 at 06:17:53 UTC, Basile B. wrote:
>> https://github.com/tonsky/FiraCode/blob/master/README.md
>> https://www.reddit.com/r/programming/comments/4zsr4y/monospaced_font_with_programming_ligatures_in/
>>
>> It doesn't looks bad with D, even if I'm not a big fan of the && and @.
>
> Bad things are waiting for you to forget a space:
>
> x<-y        (x less-than (negate y)) becomes (x back-arrow y)

Oh, yes problem here ! Though with a bit of discipline in the writing style you can avoid that (the rule would be to separate all lexical tokens with a space). I use Fira since it was announced on Reddit and didn't noticed this yet.