Who contributed to .NET on July 22, 2026?

11 developers shipped this update, including tannergooding, matouskozak, EgorBo, AbhitejJohn, rolfbjarne, jaredpar, jjonescz, and AlekseyTs, and 3 more.

What were the notable .NET updates?

Make Complex conform to C23 Annex G special values, Migrate LLM evals to the Vally harness, and Add missing Vally configs for 3 evals.

COMPLEX NUMBERS NOW IEEE 754 COMPLIANT, SKILLS EVALS GO VALLY-ONLY, UNSAFE EVOLVES

Complex<T> just shipped conformance to C23 Annex G special values, dotnet/skills completed its migration to the Vally eval harness, and the language is tightening unsafe semantics ahead of C# 13.

Complex<T> now conforms to C23 Annex G (IEC 60559) for signed zeros, infinities, and NaNs [1], filling a gap that existed because complex arithmetic sits outside IEEE 754 itself. This matters for numerical code that relies on special-value semantics in complex domain calculations. Separately, dotnet/skills retired skill-validator's evaluate command entirely, making Vally the sole LLM eval engine across PR gates, scheduled runs, and dashboard publishing [2], while retaining skill-validator's check linter pending Vally support; three skills that shipped base evals but had no Vally configs are now scored [3]. On the language front, Roslyn is implementing unsafe evolution: unsafe modifiers on delegates, static constructors, destructors, and type declarations now produce errors because they have no meaning under the new rules [4]. The JIT hardened lowering paths with no user-visible impact [5], and LibraryImportGenerator prepped for unsafe-v2 by wrapping generated stubs in unsafe blocks instead of marking containing types [6], ensuring code remains valid under both old and new unsafe rules. Pattern matching got a performance boost via Tests.ValueSet, cutting O(n^2) behavior for large or-patterns down to O(1) filter operations [7]. Debugger infrastructure pushed DAC/cDAC activation logic into dbgshim so SOS and ClrMD can request IXCLRDataProcess without duplicating location decisions [8]. Test infrastructure cleaned house: macios deleted the legacy mmptest suite targeting .NET Framework 4.7.2 and ported two relevant tests to the active test harness [9]. RemoteExecutor bumped from 7.0.0-beta to 10.0.0-beta, removing obsolete pinning [10].