lambdaclass / lambdaclass/lambda_compiler_kit
proof: add parseRaw_iff end-to-end correctness theorem
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
There is no end-to-end iff theorem connecting parseRaw / parse directly to the ValidJson spec predicate at the string level. The existing theorems operate at the token level (parseValue_iff etc.), requiring callers to reason about tokenization separately.
Expected fix
Add parseRaw_iff (and/or parse_iff):
theorem parseRaw_iff (input : String) :
parseRaw input = .ok v ↔ ... -- ValidJson characterization over input
This requires composing tokenizer correctness with parser correctness.
References
- Suggested by AI code review on PR #8
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the parseRaw and parse entry points, then read the existing parseValue_iff theorem and the tokenizer correctness results. Compose the tokenizer and parser guarantees into a string-level iff theorem characterizing ValidJson; done means parseRaw_iff and/or parse_iff states that relationship directly.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100