IronScheme VS Roslyn

I recently pushed a library to IronScheme to implement anyc / await in a way that I felt was reasonable. Before that, IronScheme had pretty limited support for concurrency, so my goal was to create a library that provided concurrency facilities in a way that would interop nicely with .NET libraries.

Apparently this costs $99/yr for a company called Apex Data Solutions to wire the freely available IronScheme into Office 365 via its extension model. See their marketing and shop pages.

I love this example: https://github.com/IronScheme/IronScheme/commit/2f847793946935bd9143cdfb064f9006f763df68

you mean IronRust, to go with IronRuby and IronPython, IronScheme, and IronJS

.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.