Search Issue Tracker
Fixed in 1.4.X
Votes
0
Found in [Package]
0.2.4-preview.45
Issue ID
1120514
Regression
No
[Burst] Uninformative compiler errors in Console Window when trying to use a foreach loop
How to reproduce:
1. Open attached project "case_1120514-BurstForeachError"
2. Make sure that "SampleScene" is opened
3. Enter Play Mode
4. Observer Console Window and Burst Inspector output
Expected result: no compiler errors appear in the Console Window
Actual result: compiler error related to "try" blocks not being supported appears in the Console Window
Reproducible with:2018.3.7f1, 2019.1.0b5, 2019.2.0a6
Could not test with: 2018.3.0a6 and older (compiler shows missing assembly reference for Burst attributes)
Reproducible with package versions: 0.2.4-preview.5, 0.2.4-preview.45
Note: changing the foreach loop into a regular for loop fixes the issue. More detailed errors than the ones shown in the Console Window after entering Play Mode can be seen in the Burst Inspector at any time
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- RenderParam.renderPriority is ignored when rendering Mesh with Graphics.RenderMesh()
- Multipage Sprite Atlas renders incorrectly when Secondary Textures are used
- Changes to the Terrain Prefab are reflected on the unrelated Terrain GameObject in a Scene when sculpting it using Brushes
- Data is not serialized correctly on time when OnValidate is used to retrieve the data
- The mouse cursor is positioned in the center when Cursor.LockState is set to CursorLockMode.Confined and changing the mouse position
Resolution Note (fix version 1.4):
Fixed in Burst 1.4, we are now supporting using pattern