-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/9.0-staging] Support generic fields in PersistedAssemblyBuilder #110839
[release/9.0-staging] Support generic fields in PersistedAssemblyBuilder #110839
Conversation
Tagging subscribers to this area: @dotnet/area-system-reflection-emit |
@steveharter friendly reminder that today's code complete for the Feb 2025 Release. Please merge this change by 4pm PT if you'd like it included in that release version. Otherwise, it will have to wait until next month. |
@rbhanda why was "servicing-consider" removed? |
@rbhanda I think your intention was to change it to servicing-approved. I can tell because you set the milestone to 9.0.2. |
@steveharter if we want this included in the Feb release, I sent you the instructions to Teams. PTAL ASAP. |
/backport to release/9.0 |
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/12796250634 |
Backport of #110372 to release/9.0-staging
/cc @steveharter
Customer Impact
The new
PersistableAssemblyBuilder
functionality added in v9 has a bug where generic fields do not generate the proper IL, causing a generic field to be generated as non-generic.Regression
This was new functionality added in v9.
Testing
The original author's repro was verified and a test added that inspects the generated field's metadata to make sure the field is generic.
Risk
Low; the fix is fairly straightforward and follows other similar cases where we need to use metadata from open generic types instead of the closed generic type.