scriban VS boo

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.

https://github.com/scriban/scriban I'm not sure it's equal Go template.

What if text templates were just another asset in the Unity Editor? And could be used to generate code or any text asset. This is what I set out to accomplish with Templ. An open-source Unity Editor extension which integrates Scriban templates to enable declarative text assets generation effortlessly.

That's a well trodden path in most languages. A cursory search surfaced this library that looks like it would probably do the job:

https://github.com/scriban/scriban

I've come across scriban template language but it does not have any watch feature. Maybe I'll hook it up with some File Watcher API of dotnet (if it exists) and see how it goes.

Scriban or FluentEmail's renderers might be just what you're looking for.

There's also boo-lang which was quite nice for DSLs / configuration.

An age ago I used to be a huge fan of the Boo programming language, a .NET runtime language that was vaguely python-ic.

One of the great features I loved was it's metaprogramming capabilities. Among others, like E, the quasi-parser was easy to reach for & use at runtime. The tests are a good way to see Boo features, here's a quasi-quote test, which uses a Quasi-quote to get some code, then adds to that AST imperatively: https://github.com/boo-lang/boo/blob/master/tests/testcases/...