standard VS Roslyn

Why are you targeting .NET Standard 1.5? This document says PCL profile 151 maps to .NET Standard 1.2 but at this point I think everyone should be on 2.0.

Mais detalhes sobre as versões 🎯 .NET Standard 2.1 https://github.com/dotnet/standard/blob/master/docs/versions/netstandard2.1.md

If you still don't believe that Standard is dead, look at when the latest version was announced: 2018-11-05, over two years ago. Since that time there have been three full releases of Core/5.0 (2.2, 3.1, 5.0) and the preview of 6.0. It's quite clear where Microsoft's priorities are. Or look at the most recent activity on the .NET Standard repo: 2020-05-22, over 10 months ago.

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.