Bug Burst error BC1020 for Flags

> (0,0): Burst error BC1020: Boxing a valuetype `Components.FooFlags` to a managed object is not supported

Why there is no transparency compiling for flags enum
I can use constants, but its not so convenient

Components.FooFlags:

Code (CSharp):

1.  
2. [Flags]
3. public enum FooFlags: int
4. {
5.     DETACHED = 1 << 1,
6.     READY = 1 << 2
7. }
8.  

 

"boxing to managed object" sounds to me as if you are adding a FooFlags variable to a managed object such as a List or Dictionary where boxing occurs (collections only store reference types, therefore value types like enums are boxed into an object).

can you post the code that uses FooFlags?

 

Maybe you are using flags.HasFlag? This method generates garbage and uses boxing.

 

Yes, i using HasFlag

It is unclear to me why burst does not know how to work with such code

 

Because Unitys current version of the system library's HasFlags looks like this.

Code (CSharp):

1. public bool HasFlag(Enum flag)
2.     {
3.       if (flag == null)
4.         throw new ArgumentNullException(nameof (flag));
5.       return this.GetType().IsEquivalentTo(flag.GetType()) ? this.InternalHasFlag(flag) : throw new ArgumentException(Environment.GetResourceString("Argument_EnumTypeDoesNotMatch", (object) flag.GetType(), (object) this.GetType()));
6.     }

which is very not burst usable.

 

There is an unsafe code version for hasFlag() here, I don't understand it but it seems to work, even in Burst.
https://stackoverflow.com/questions/11665279/why-enums-hasflag-method-need-boxing

 

Damn...
They could make a plug for that... ̶p̶u̶r̶p̶o̶s̶e̶ ̶o̶f̶ ̶t̶o̶o̶l̶ ̶i̶s̶ ̶t̶o̶ ̶e̶a̶s̶e̶ ̶t̶h̶e̶ ̶f̶a̶t̶e̶ ̶o̶f̶ ̶d̶e̶v̶e̶l̶o̶p̶e̶r̶,̶ ̶n̶o̶t̶ ̶t̶o̶ ̶f̶o̶r̶c̶e̶ ̶h̶i̶m̶ ̶t̶o̶ ̶d̶o̶ ̶k̶l̶u̶g̶e̶ ̶.̶.̶.̶

Solution from @Arnold_2013 is good for me, thanks.