Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.5p4
Issue ID
811572
Regression
No
Compiler does not allow implicit conversions in a ternary operator
Steps to reproduce:
1. Open attached project ("New Unity Project1").
2. Notice that the "Console" window outputs:
"Assets/test.cs(11,16): error CS0172: Can not compute type of conditional expression as `int' and `ushort' convert implicitly to each other"
Expected result:
The compilation should allow implicit conversions in a ternary operator.
Note:
Creating a console application in Visual Studio 2015 with the same lines of code and running it works fine.
Reproduced with:
5.3.5p6, 5.4.0b25.
Workaround:
Implicitly cast the value to be of the same type. In this case:
int a = 0;
ushort b = 0;
a = true ? 0 : (int)b;
-----------------------------------
The issue will be solved as part of compiler upgrade.
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