com.unity.burst 1.7.4

📈 Improvements

• Entry point functions weren't always included in crash callstacks; now they are

🔧 Bug Fixes

• Interface methods where not being hashed correctly for constrained types, which would result in burst failing to recompile code that had changed in an implementation class.
• Fixed a safety check bug with `Span`/`ReadOnlySpan` and `Slice(start, length)` where if `start` + `length` was equal to the `Length` of the original span, the safety check would incorrectly report an out-of-bounds access.
• Corrupted binary could be produced on M1 if there was not enough space for UUID+codesign injection.
• Linking issue when exports differ only by module.
• Disabling Burst from the command line via `--burst-disable-compilation` no longer results in Burst errors when building a player for Android
• ;'s in paths would cause burst to fail. Note - Also requires a fix in the Editor, so if your project has ;'s in its path, the workaround is to remove the ; from the folder name for now.
• Fixed error when compiling assemblies with spaces in their names
• Fixed access violation race condition bug
• Fixed a bug where static fields in generic types could in some situations be initialized with the incorrect value
• Fixed that UWP builds wouldn't respect the specified "Target SDK Version" and "Visual Studio Version" settings
• Fix error that occurs with a specific formulation of IL, using xx with an early out escape and unbalanced calculation stack. (Object reference not set to an instance of ... in CollectBlock.ToVisitOrder)
• Fixed a bug with locally declared array variables in functions where storing `null` into them could cause invalid codegen.
• Fixed a bug in Burst player builds where sufficiently complicated Bursted code could cause a deadlock deep within LLVM.
• An Internal Compiler Error that could occur if a function that requires a struct ret (due to ABI) has been discarded by other logic.

✨ Features

⚡ API Changes

⚠️ Known Issues