Search Issue Tracker
Fixed in 2017.3.X
Votes
0
Found in
5.6.0f2
Issue ID
899417
Regression
No
Error 'use of unassigned variable' is thrown in console only when an unrelated "else" block is written
Monodevelop and visual studio detect an error, yet Unity ignores it.
Steps to reproduce:
1. Open attached project
2. Open "ElseBug.cs" script
3. Comment out 22 line which has empty else block
Result: No error in console
Expected result: 'use of unassigned variable' error should be shown regardless the else block exist or not
Note: You can make error appear by uncommenting else block in 22 line
Reproduced on: 5.5.2p2, 5.6.0f2, 2017.1.0b7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment