csharp12-features-guide

C#12 collection expressions in Unity 6 do trigger GC allocations, making them unsafe for hot-paths. You should restrict collection expression initialization to setup phases rather than Update loops to prevent frame-rate drops.

Primary constructors in Unity 6 CoreCLR provide cleaner syntax without adding runtime overhead. They are safe for hot-path execution when used correctly, though you must understand their specific GC implications to avoid unnecessary allocations.

The safest way to use Span<T> in Unity 6 is to leverage it for memory-safe operations that avoid GC allocations. This Skill guides you through Span<T> idioms and their performance implications to ensure hot-path safety in your game loops.

Unity 6 with CoreCLR supports ref readonly parameters to prevent unnecessary data copying. This feature is detailed for Unity-specific use cases, allowing you to safely pass large structs without allocating memory on the garbage collected heap.

You should avoid using new C#13 language features in Unity hot-paths if they trigger GC allocations, such as improper collection expression usage. This guide identifies these constraints, helping you restrict allocation-heavy features to initialization phases.

You need a solid understanding of C# language fundamentals and Unity development practices to implement C#12 features. This guide builds on that foundation to explain Unity-specific rules, GC implications, and hot-path safety for modern language features.