| ▲ | simonw 6 hours ago | |||||||
I went looking for a single Markdown file I could dump into an LLM to "teach" it the language and found this one: https://github.com/jordanhubbard/nanolang/blob/main/MEMORY.m... Optimistically I dumped the whole thing into Claude Opus 4.5 as a system prompt to see if it could generate a one-shot program from it:
Here's the transcript for that. The code didn't work: https://gist.github.com/simonw/7847f022566d11629ec2139f1d109...So I fired up Claude Code inside a checkout of the nanolang and told it how to run the compiler and let it fix the problems... which DID work. Here's that transcript: https://gisthost.github.io/?9696da6882cb6596be6a9d5196e8a7a5... And the finished code, with its output in a comment: https://gist.github.com/simonw/e7f3577adcfd392ab7fa23b1295d0... So yeah, a good LLM can definitely figure out how to use this thing given access to the existing documentation and the ability to run that compiler. | ||||||||
| ▲ | e12e 4 hours ago | parent | next [-] | |||||||
Oh, wow. I thought the control flow from the readme was a little annoying with the prefix -notation for bigger/smaller than;
But that's nothing compared to the scream for a case/switch-statement in the Mandelbrot example... | ||||||||
| ||||||||
| ▲ | nodja 6 hours ago | parent | prev | next [-] | |||||||
I think you need to either feed it all of ./docs or give your agent access to those files so it can read them as reference. The MEMORY.md file you posted mentions ./docs/CANONICAL_STYLE.md and ./docs/LLM_CORE_SUBSET.md and they in turn mention indirectly other features and files inside the docs folder. | ||||||||
| ||||||||
| ▲ | hahahahhaah 5 hours ago | parent | prev [-] | |||||||
But are you losing horsepower of the LLM available to problem solving on a given task by doing so? | ||||||||
| ||||||||