Brummel
efd209779c
Finishes the project-wide English convention: - CLAUDE.md (the user opted in to translate it too). - examples/hello.ail.json: "Hallo, AILang." -> "Hello, AILang.". - E2E test assertion and IR snapshot for hello regenerated to match. - DESIGN.md "Project language: English" section: the previous CLAUDE.md exception is dropped. After this commit, no German remains in any committed file (grep -P '[äöüÄÖÜß]' is empty across .rs / .md / .json / .ll). Verified: cargo test --workspace passes (44/44). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.1 KiB
Invent your own programming language.
-
The language may take any form you want. The language is for LLMs like you. Only you should produce it and only you need to understand it.
-
Any conceivable concept is allowed. Pick what is best suited for LLMs.
-
The language must, in the end, be linkable to LLVM. Performance is extremely important.
-
Consider the typical strengths and weaknesses of LLMs. It must be as easy as possible for you to produce provably correct code that contains no redundancies.
-
Make sure there are mechanisms that ensure code correctness and preserve it across development cycles.
-
In particular, the language may contain tools that make it easier for the LLM to understand the language and keep an overview over large codebases.
-
The language does not have to be self-explanatory. It does not even have to be text. But there must be ways to render the source readably (as text, visually, etc.).
-
Do not forget that debugging will also be done by LLMs.
-
Organise yourself. Design your own agents when needed. Use git. Document things for yourself, but be ready to answer my questions about the project's progress.