Do not suggest using foreach in Burst compiled jobs

[UnknownDude1]

Hello,

I've been having this issue that Rider keeps suggesting me to use features in Burst-compiled jobs that are unsupported. The best example is the suggestion to replace a for loop with foreach, which is unsupported by Burst. Another example would be the usage of Linq, which is also unsupported.

So far I've been dealing with this issue by simply adding the Resharper disable comments, but this is something that I think should not be necessary.

Cheers

[Lattyware]

Yeah. Ideally full support would include showing errors in burst compiled code where such features are used. Other examples:

• Showing errors when using try/catch or using.
• Showing errors when using instances of managed types.
• Showing errors when writing to static fields.
• Showing errors when using StructLayout Auto types in burst compiled code (most common case is ValueTuple).
• Suggest using Unity.Mathematics for mathematics where possible.

The full restrictions can be found at https://docs.unity3d.com/Packages/com.unity.burst@1.2/manual/index.html#cnet-language-support.

[krasnotsvetov]

Thank you for your feedback. We have big internal task to support Burst compiler

Please share any feature requst for Burst support here :)

[Domonion]

Hello @Lattyware and @UnknownSoldier1!
Thank you for your feedback, as you might have already seen we have added some support for the Burst compiler. From the next EAP, there will be code vision that will show if the function is in the Burst context or not.

Here is an example:

Also, there is context action and quick fix to place the BurstDiscard attribute.

If you have further suggestions on what to support at Burst - feel free to post it at YouTrack or add here at repo as an issue.

[Domonion]

@Lattyware I created issues based on your suggestions, it would be great you would provide a code example to support for each suggestion. #1900 #1901

[Domonion]

#2015 from now foreach is allowed in burst compiled code, closing issue