Meta Issue: problems with the F# version of F* (currently lagging behind the OCaml version)

[catalin-hritcu]

Turning this into a meta-issue. All these problems with the F# version don't appear in OCaml version:

• Parsing: one additional shift-reduce conflict (The parser is different between the F# and OCaml versions #672)
• Parsing: bizare context sensitive parsing for requires True (Very strange sporadic problem parsing (requires True); dependent on larger context; now only in F# build #252) and dependent tuples (Spurious syntax error with dependent pairs (only occuring with FSharp build) #404)
• Parsing: <> are not parsed as type application in the first definition of a file with the menhir generated fsyacc parser (reported in more detail in The parser is different between the F# and OCaml versions #672)
• Hints: not currently supported, requires a JSON parser (Extend support for hints to F#-compiled version of F* #633) -- this prevents verifying the test suite since --use_hints is passed by default by our makefiles. Fixed by @wintersteiger in F#/managed hints #840
• Integers: normalization of integer operations requires moving to big ints in .NET, which we should anyway do for soundness (F# build of F* still uses bounded machine integers for ints #1054)
• Floating point literals are badly handled by the F# extraction mechanism (Floating point literals are badly handled by the F# extraction mechanism #793)
• Interactive mode not working with the F# version
  version-to-list: Invalid version syntax: ‘’ (must start with a number)
• Autodeps: F# and OCaml versions used to process files in different order (see Stabilized topological sort of file dependencies. #871)
• No support for --indent (--indent doesn't yet work for the F# version #874)
• FStar.UInt discrepancy (FStar.UInt discrepancy #872)
• Cannot make ulib (ulib doesn't make with F# build of F* #1023)
• Problem with trailing spaces on set-option (Trailing space on set-options confuses F# build. #1051)

[kyoDralliam]

The additional shift-reduce conflict is a known bug in fsyacc (fsprojects/FsLexYacc#39) due to a bad handling of non-associative-ness.
The next 2 bugs were caused by bad range queries in the parser and are fixed in kyod_parser.

[cpitclaudel]

I ticked off the "interactive mode" box; I fixed that some time ago.