dwarfcorp VS Roslyn

No, a backing field is not always present. Properties are just a pair of functions disguised as a field. They have all the same implementation restrictions of a function when it comes to having a backing field - that is, none. Look at the example here of what properties actually are very good at: https://github.com/Blecki/dwarfcorp/blob/master/DwarfCorp/World/Voxels/VoxelHandle.cs Do you think the Voxelhandle type has a bunch of backing fields taking up space in it? It has 10+ properties all derived from data stored somewhere else.

My understanding is that the .NET team is working toward this with Interceptors: https://github.com/dotnet/roslyn/blob/main/docs/features/int...

.NET is a little smarter about switch code generation these days: https://github.com/dotnet/roslyn/pull/66081

Recently, while creating some experimental C# source code generators (xafero/csharp-generators), I was just concatenating strings together. Like you do, you know, if things have to go very quickly. If you have a simple use case, use a formatted multi-line string or some template library like scriban. But I searched for a way to generate more and more complicated logic easily - like for example, adding raw SQL handler methods to my pre-generated DBSet-like classes for my ADO.NET experiment. You could now say: Use Roslyn and that's really fine if you look everything up in a website like SharpLab, which shows immediately the syntax tree of our C# code.

At runtime, the Case C# expressions are embedded into a function and dynamically compiled into an assembly using the Roslyn C# compiler. Then the function that contains the expression is called (e.g. CaseAvailableFunction.Availablle()). At runtime, the function provides various methods to access stored case values as well as the current input data.