Cascadia-code: Feature Request: remove break between two = when enable ligatures

[Sherlock-Holo]

Description of the new feature/enhancement (with images if possible)

when enabling ligatures, the old version font will display == like

however, updated to the latest version, it displays like

please revert this change, the reason why people enable ligatures are that they don't want to see a break between ==, if someone wants to see the break, why don't they disable the ligatures?

If doesn't revert this change, please offer a subversion that there is no break between two =

[aaronbell]

Initially, I thought the same as you—that if you don't want ligatures, just turn them off. However, at the end of the day, legibility must trump any beautification of the code via ligatures.

As you read on the other thread, the concern is that = and == have a similar-enough length to one another that when glancing through code it can be easy to mistake one for the other. I've experienced that issue myself. So it makes sense to include a break there as a visual reinforcement of the code.

I'm open to consider adding a stylistic set that will enable you to switch to a non-broken version, though support for such functionality is dependent on the coding environment.

[Sherlock-Holo]

I usually write golang and rust, both of them a==b is a bool, and a=b is a statement, it doesn't make me confused, besides the =='s length is not equal =, that reduces the possibility of confusion.

If you could add a non-broken version, I will be very grateful