| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Tagging subscribers to this area: @dotnet/area-system-reflection-emit |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
|
@rbhanda why was "servicing-consider" removed? |
Sorry, something went wrong.
|
@rbhanda I think your intention was to change it to servicing-approved. I can tell because you set the milestone to 9.0.2. |
Sorry, something went wrong.
|
@steveharter if we want this included in the Feb release, I sent you the instructions to Teams. PTAL ASAP. |
Sorry, something went wrong.
|
/backport to release/9.0 |
Sorry, something went wrong.
|
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/12796250634 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.