You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming this is the behavior of this trailing semicolon, how bad is it? who or what piece of code is affected by it? why should someone invest time and effort tracking it down and changing it?
Because when writing alternative parser for ocaml, it might be a nightmare to
get the same position as OCaml. And then when you test, it is hard to distinguish
the differences that are important and those that are irrelevant (like this one).
I will try to see if it is easy to fix and submit a pull request ...
Original bug ID: 7619
Reporter: ChriChri
Status: resolved (set by @xavierleroy on 2017-10-18T15:11:43Z)
Resolution: fixed
Priority: normal
Severity: tweak
Version: 4.05.0
Fixed in version: 4.06.0 +dev/beta1/beta2/rc1
Category: lexing and parsing
Monitored by: ChriChri @gasche
Bug description
Compiling the following
let f x y = x y; x y;
Produce the following position for the first application:
And this for the second:
The semicolumn is part of the last application, which look wrong
Steps to reproduce
compile the above line with -dparsetree
The text was updated successfully, but these errors were encountered: