Search Issue Tracker
Fixed in 2021.2.X
Votes
2
Found in
2019.4
2019.4.3f1
2020.1
2020.2
Issue ID
1263117
Regression
No
Compiler wrongly detect unmanaged structs as containing nullabe fields
Reproduction steps:
1. Open the user's attached project
2. Inspect Console
Expected result: No "CS8377" errors are thrown
Actual result: "CS8377: the type struct must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method" error is thrown
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Couldn't test with 2018.4 (ECS is not supported)
Reproducible with package versions: 0.11.1-preview.4
Couldn't test with newer package versions (project errors after upgrade due to API changes)
Note: on 2020.2.0b1, different errors are thrown ("error CS0121: The call is ambiguous between the following methods or properties")
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment