Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type checker: don't suppress errors while checking expressions #18311

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

auduchinok
Copy link
Member

Fixes #17787.

I guess many tests may need to be updated. 🙂

@auduchinok auduchinok requested a review from a team as a code owner February 12, 2025 17:41
Copy link
Contributor

github-actions bot commented Feb 12, 2025

❗ Release notes required


✅ Found changes and release notes in following paths:

Change path Release notes path Description
src/Compiler docs/release-notes/.FSharp.Compiler.Service/9.0.300.md

@psfinaki
Copy link
Member

Well - 11 tests, that's much less than I would have expected here :)

@@ -16,6 +16,7 @@
* Add support for C# `Experimental` attribute. ([PR #18253](https://github.com/dotnet/fsharp/pull/18253))
* Nullness warnings are issued for signature<>implementation conformance ([PR #18186](https://github.com/dotnet/fsharp/pull/18186))
* Symbols: Add FSharpAssembly.IsFSharp ([PR #18290](https://github.com/dotnet/fsharp/pull/18290))
* Type checker: don't suppress errors while checking expressions ([PR #18311](https://github.com/dotnet/fsharp/pull/18311))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will need better real-life IDE tests and what it does when typing incomplete snippets of code.
I assume there was a reason to suppress typecheck errors in case of parser errors, to prevent a wall of semantic errors jumping around when typing.

I admit the reasons behind it might have changed, but it would be safer if we could either test this more while typing.

@auduchinok auduchinok force-pushed the tcExpr-noErrorSuppress branch from e025765 to a8c081a Compare February 20, 2025 18:32
@auduchinok
Copy link
Member Author

auduchinok commented Mar 13, 2025

Could someone please help me with updating the baselines here? I've tried committing the files produced during the local tests run, but it doesn't seem to succeed on CI.

@Martin521
Copy link
Contributor

Martin521 commented Mar 13, 2025

This does not look like a baseline issue, all the CI runs today had these failures.
See also here.

EDIT: sorry, forget that, seems to be different

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

Successfully merging this pull request may close these issues.

Type checker errors should be reported when syntax errors are present
4 participants