Skip to content

Conversation

@auduchinok
Copy link
Member

Fixes #15452.
Also adds an ignored type checking pass to the syntax tree tests to ensure that the type checker doesn't fail on the produced trees.

@auduchinok auduchinok requested a review from a team as a code owner June 21, 2023 13:03
@auduchinok
Copy link
Member Author

It's ready.

@auduchinok auduchinok force-pushed the syntaxTree-tests-runTc branch from a07f84a to a01333d Compare June 21, 2023 14:15
@abonie
Copy link
Member

abonie commented Jun 22, 2023

Could you add some integration tests to make sure VS does not blow up as described in the original issue?

@auduchinok
Copy link
Member Author

auduchinok commented Jun 22, 2023

@abonie I've added such a check here: https://github.com/dotnet/fsharp/pull/15458/files#diff-e3b9dc1544df780246fc6ce79b6a1ff795afb95afd8a57b57aa99884dc35c6f2R203. It throws the same exceptions as VS would. I don't think we want to duplicate all the parser tests with VS ones, so having an assert in them seems a good way to check it.

The cases initially reported in #15452 have already been covered by the parser tests (and they did fail when I added this check).

@psfinaki psfinaki merged commit c422e70 into dotnet:main Jun 22, 2023
@auduchinok auduchinok deleted the syntaxTree-tests-runTc branch June 22, 2023 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Internal error when typing in VS

4 participants