lipstick VS interface99

Repo

There is a project that achieves something like this, and quite nicely I think, worth checking it https://github.com/Hirrolot/interface99

I agree; I would especially not recommend abusing macros throughout an application codebase too much. Conceptually, Metalang99 is more of a (sub)language than a library, which also adds some entry barrier. Ideally, I see the application of Metalang99 being used "behind the scenes", e.g., encapsulated in separate code files/libraries such as Datatype99 and Interface99. This is what I (mostly) do in SmolRTSP.

There are also some differences. Golang, for example, can resolve interface methods at run-time, whereas Interface99 constructs virtual tables statically. Interface99 allows default implementations; Golang doesn't. And, of course, Interface99 mandates placing impl(MyIface, MyType), whereas Golang uses a.k.a. duck typing for interfaces (interface implementations are indistinguishable from ordinary methods). Also, when you would use embedding in Golang, such as this:

I think your github repo link is broken. Here's a working link.

I've done something similar with Datatype99 and Interface99. They are like a macro eDSL that compiles to C. The first one features algebraic data types, the second one features interfaces.

If you need a bit more high-level constructions, you can use the Datatype99 and Interface99 libraries. The former provides polymorphism over data, the latter -- over behaviour (I am the creator of these libraries).

Is it possible that you could benefit from "a better C"? If so, I'd love to hear your take on Crystal, and the recent announce on Interface99.

There is a full example code: https://github.com/Hirrolot/interface99/blob/master/examples/state.c.