| I accidentally ended up designing something that can probably be called a meta-programming language. Repo:
https://github.com/ewiger/len `len` is an experiment in making specifications more central than code itself. The rough model is: * write intent and examples in natural language
* capture the core structure with types, relations, and contracts
* describe how that model should map to concrete generated code In the repo I currently call those layers L0, L1, and L2. This is very much an early project. The current tooling is a small Go CLI that validates the structure of `.l1` files, and the language design is still evolving. So this is not a polished “look what I built” launch. I’m sharing it because I’d like honest feedback on whether the core idea is interesting, confused, redundant with existing tools, or maybe useful in some narrower niche. Comments, criticism, and pointers to similar work would be very welcome. |