Type checker: recover on checking binding parameter constraints #19046
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
❗ Release notes required
|
auduchinok
force-pushed
the
tc-recover-contraints2
branch
from
39b46c8 to
e74b246
Compare
Member
Author
|
This is ready |
T-Gro
reviewed
Nov 6, 2025
T-Gro
reviewed
Nov 6, 2025
auduchinok
force-pushed
the
tc-recover-contraints2
branch
from
e04fa56 to
6b91fdf
Compare
Member
Author
|
This is ready. |
Removed the test case for 'neg68' from MigratedTypeCheckTests.
T-Gro
approved these changes
Nov 11, 2025
github-project-automation
bot
moved this from New
to In Progress
in F# Compiler and Tooling
github-project-automation
bot
moved this from In Progress
to Done
in F# Compiler and Tooling
vzarytovskii
approved these changes
Nov 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a more conservative version of #19034. The previous PR unexpectedly changes behavior in some cases where exceptions during analysis were a part of the control flow, so should be done more cautiously by going through each affected place separately. This PR adds a silent recovery for the single place where the previous PR was started.
In the following example
fwas not added to the environment, breaking analysis of its usages: