Weird context sensitive error in FStar's parse about fslexyacc

[kyoDralliam]

I just found out where the error was comming from : I was using erroneous queries on the position of tokens. I guess I have been misled by the different behaviour of ocamlyacc/menhir which seems to return the range information for the current production and silently drop any incorrect range request.

Also I just realised that FStar was dropping the raised exception :
error : System.NullReferenceException: Object reference not set to an instance of an object
which comes from a call to parseState.InputRange(n) (parseState being a Microsoft.FSharp.Text.Parsing.IParseState).

Edit : after looking at the ocaml stdlib I don't see any mechanism to "correct" the wrong position. I guess it was just a bad coincidence that the behaviour did appear with fsyacc and not with ocamlyacc...

[cartermp]

@kyoDralliam Sorry nobody really answered this. I assume that 3.5 years later this isn't really a problem anymore, so I'll close this issue out.