Skip to content
This repository was archived by the owner on Jun 15, 2023. It is now read-only.

Type annotations and ligatures #181

Closed
jfrolich opened this issue Nov 23, 2020 · 1 comment
Closed

Type annotations and ligatures #181

jfrolich opened this issue Nov 23, 2020 · 1 comment

Comments

@jfrolich
Copy link

Type definitions can trigger ligatures that exists in many popular code fonts:

let foo = (~a: option<array<int>>=?) => ...

Not sure if this is a huge concern, but perhaps we can format in a way that doesn't trigger the ligature and is also more pleasant on the eyes?

let foo = (~a: option<array<int>> = ?) => ...
@jfrolich jfrolich changed the title Type definitions and lignatures Type annotations and ligatures Nov 23, 2020
@chenglou
Copy link
Member

chenglou commented Dec 5, 2020

Thanks. This is a VSCode bug. Merged into rescript-lang/rescript-vscode#35

@chenglou chenglou closed this as completed Dec 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants