Repository navigation
Wrong emitted metadata for nested generic types #17797
Description
Activity
Try with realsig-
@vzarytovskii Can confirm it helps, thanks!
@vzarytovskii Can confirm it helps, thanks!
Thanks. We turned it off by default in rc2, but compiler itself still builds with realsig
Yes this is real ... needs fixing.
This is fixed in rtm (by rolling back the realsig), @KevinRansom do you want to keep it open to track the fix with
realsig+?@vzarytovskii i do want to keep it open.
- added a commit that references this issue
on Jan 14, 2025
Metadata
Metadata
Assignees
Type
Projects
- Status
The generated types for (at least some) closures miss type parameters from their containing types.
When defining a nested type, it should redefine all type parameters from its containing type (see I.10.7.1 from ECMA-335).
Closures like
Internal.Utilities.Collections.AgedLookup`3+-ctor@25-5miss their parent's type parameters and have only 1 of the 4 type parameters needed. This was caught by an assert in R#/Rider metadata reading code. We're disabling the assert for now, but it looks like the code generation should be fixed on the F# compiler side.