Looking at the errors, it appears that the following 3 tests are failing; some advice on how to proceed with regards to them would be appreciated.

@liboz Those errors appear harmless and you can just make test fixes (we'll review the test fixes in any case)

The typecheck\sigs test is actually about 200 tests, and I believe it stops on first failure. So you might have to wade through a whole bunch of updates. If possible try to run these on your local machine. We should really break this out into 200 independently failing tests (if you get a chance to do that... :) )

I cleaned up the git history a bit and fixed all the relevant tests.

I messed up my previous chart with regards to which was expected/new. Here's a new one for all the failing tests:

It seems the additional error might be because of the extra errorRecovery. So maybe the error path should just be ().

When running the tests without the errorRecovery, I found that although the previous FSharp test suites don't need additional modification, the following code let simpleLibraryCall10 inps = Seq.map id inps apparently becomes a potential critical tailcall, which seems quite baffling.

@dsyme Is there any chance of this making F# 4.1? And/or getting into FCS so that Ionide can benefit?

I'll close/reopen to trigger CI

@dsyme The first time CI ran, there were unexpected errors such as on E_NullableOperators01, but I was unable to replicate on my computer so I rebased and this time the CI passed.

@dsyme, @KevinRansom Any chance this can be reviewed?

This is a good change and will make a significant difference in intellisense accuracy for erroneous code.