4 ms·
i've had a related question recently but it didn't get much traction https://news.ycombinator.com/item?id=47543324 https://news.ycombinator.com/item?id=4754332
by midnight_eclair 6mo ago
i've had a related question recently but it didn't get much traction
https://news.ycombinator.com/item?id=47543324 https://news.ycombinator.com/item?id=47543324
what's the point of markdown? there's nothing useful you can do with it other than handing it over to llm and getting some probabilistic response
- 1st1 6mo agoRead this section, I've just updated it to be more clear, hopefully will answer your question: https://github.com/1st1/lat.md?tab=readme-ov-file#the-idea https://github.com/1st1/lat.md?tab=readme-ov-file#the-idea
- midnight_eclair 6mo ago> Test specs with enforcement — test cases can be described as sections in lat.md/ and marked with require-code-mention: true. Each spec then must be referenced by a // @lat: comment in test code. lat check flags any spec without a backlink, so you can review and maintain test coverage from the knowledge graph. if you mean this paragraph - imo that's still too hand-wavy compared to enforcement through generative tests for spec conformance.
- 1st1 6mo agocan you tell me more about what you mean by generative tests for spec conformance?
- midnight_eclair 6mo agotests generated based on normative spec to validate if the implementation accepts the right inputs, rejects the wrong ones, produces correctly shaped outputs and to some extend also validates behavior. normative specs allow generation of such tests deterministically - no need to spend tokens, no risk of hallucinations, much higher level of confidence that generated code is correct and much more accurate feedback from the test system into the LLM loop.