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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment