Fix SRTP type inference regression: ApplyDefaults now solves typars with MayResolveMember constraints #19222
+1
−0
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.
Fixes SRTP type inference regression where
curryN-style patterns worked in SDK 8.0 but failed with FS0030 (value restriction) in SDK 9.0+.Root Cause
PR #15181 introduced
FreshenTyparwhich clearsStaticReqtoNonewhenInterfacesWithAbstractStaticMembersis enabled. SRTP typars retained theirMayResolveMemberconstraints but lost theStaticReqmarker thatApplyDefaultsrelied on to identify them.Fix
Extended
ApplyDefaultsinCheckDeclarations.fsto explicitly check forMayResolveMemberconstraints:This ensures SRTP typars are solved regardless of whether
StaticReqis preserved through freshening.Verification
curryN-style SRTP patterns💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.