Syntax Highlighting Dying in certain instances about vscode-reasonml

I submitted another fix which I think finally resolves this. Let me know if it doesn't and I'll re-open.

[kennetpostigo]

@freebroccolo I realized the culprit is wrapping the function body in {...}

I take those away and everything is good, is this a difficult fix to make?

I suspect the issue may be related to the :: for punning which initially causes it to fail. What happens if you try something like paths::paths?

[kennetpostigo]

@freebroccolo you are right, once I do that the highlighting returns. However refmt will automatically return it to the punned labelled arguments version.

Yeah, the syntax highlighting hasn't been updated for punned arguments yet. I was working on a rewrite of the syntax highlighting that is more accurate but I haven't had a chance to finish it yet. I'll try to spend some time on that next week.

[kennetpostigo]

@freebroccolo Awesome!

@kennetpostigo Can you check if this is fixed for you now with the latest commit and whether you notice any new breakage? Just clone the repo, open repo director in code, and hit F5 to launch a development version of the extension, then try it on a file that was messed up before.

Looks like the fix I introduced needs a little more work actually.