Burst inspector showing methods that shouldn't be there

Unity Engine
,
1

Unity 2021.3.16f1
Burst 1.7.4

The following method should be excluded when collections checks are off (ENABLE_UNITY_COLLECTIONS_CHECKS is false)

8751958--1185853--upload_2023-1-23_17-34-40.png
8751958--1185853--upload_2023-1-23_17-34-40.png946×306 25.1 KB

8751958--1185841--upload_2023-1-23_17-28-38.png
8751958--1185841--upload_2023-1-23_17-28-38.png1415×135 38.9 KB

And yet calls to it show up in the decompiled code…

8751958--1185850--upload_2023-1-23_17-32-49.png
8751958--1185850--upload_2023-1-23_17-32-49.png1345×1141 158 KB

2

Hi @burningmime , does this issue also occur on Burst 1.8.2?

3

Just checked, and yes it does.

I can submit a repro project if it would be useful.

4

Actually, looking at this a bit more thoroughly, I realize this is expected behavior. Burst can’t know that your methods are considered safety-checks, because they’re not annotated as such. They’re only either included and excluded from the code that Burst compiles (based on whether ENABLE_UNITY_COLLECTIONS_CHECKS is set) before Burst gets it. The way Burst knows whether something is a safety-check is by annotating it with [Conditional("ENABLE_UNITY_COLLECTIONS_CHECKS")], so you can try that.