Well that seems to be a bug, tho are you sure it doesn’t work? I.e. is there an actual failing case? Because int and uint should have the same in-memory representation. If that’s not the case - please report an issue. C# target is a bit undermaintained at the moment, but we still want to be aware of all the casting cases for the potential CIL target ^^
It actually fails in C# when I send a -1 there for some reason, which was surprising due to the as you said same memory representation. It fails with overflow
onUncaughtError : [{ id : 0, message : OverflowException: Value was either too large or too small for an Int32., stackTrace : System.Convert.ToInt32 (System.UInt32 value) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.UInt32.System.IConvertible.ToInt32 (System.IFormatProvider provider) (at <437ba245d8404784b9fbab9b439ac908>:0)
haxe.lang.Runtime.toInt (System.Object obj) (at C:/HaxeToolkit/haxe/std/cs/internal/Runtime.hx:146)