Consider trading usage of Reflection.Emit with Source Generator in System.Text.Json

[am11]

After witnessing a bug with runtime IL emission in System.Text.Json: #40878, I read about C#'s new feature, Source Generator, and was wondering if there are considerations to completely switch to Source Generator in S.T.J? In addition to the fact that it will make things AOT-friendly (and performant), it would also help catching the typecasting issues during the compile time.

An alternative idea is #40620 - to verify generated IL on runtime.

However, I think S.T.J is the top candidate to get SourceGenerator-based implementation, since its description states:

The System.Text.Json namespace provides high-performance, low-allocating, and standards-compliant capabilities to process JavaScript Object Notation (JSON), which includes serializing objects to JSON text and deserializing JSON text to objects, with UTF-8 support built-in.

[gfoidl]

--> dotnet/runtimelab#16 (there's an experminent over there).

[am11]

Noice 😎
this is exactly what I was hoping to find.