Repository navigation
Conversation
…first) ECMA-262 es2026 at 0248456c: section 11.1, section 12 (goal symbols, white space, comments, tokens, names, punctuators, numeric, string, regular expression and template literals with SV, TV and TRV) and Annex B.1.1 HTML-like comments, with the longest-element rule and the two lexical early errors. Facts proven about it (longest-element search, trivia skip bounds) and evaluated examples. Records one erratum (the missing MV of the escape 0 before 8 or 9). Tier stays 0: no implementation. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ken (7.2) Contract predicates in terms of the spec (totality, span coverage, agreement, the line-terminator flag) and a contract-only trait with the requires and ensures; no implementation, no escape hatch. Tier stays 0. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The pinned spec does define the MV of LegacyOctalEscapeSequence :: 0 (0) in the MV clause of §12.9.3.2, so nothing was missing. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
atiernan
had a problem deploying
to
full-verification
November 16, 2026 15:49 — with
GitHub Actions
Error
atiernan
had a problem deploying
to
full-verification
November 16, 2026 23:38 — with
GitHub Actions
Error
CI's proof job requires a mutations.json for every crate Verus checks. Four mutations of the spec, each killed by a proven example: dropping <LS> from LineTerminator, adding NEL to it, the wrong MV for `b`, and dropping the recursive LegacyOctalIntegerLiteral alternative. Adds the two examples they contradict (line terminators, hex digit values). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
atiernan
temporarily deployed
to
full-verification
November 17, 2026 21:00 — with
GitHub Actions
Inactive
…e them CI's mutation step (first proof run of this crate) failed: the kill certificates for hex-digit-value-lowercase-offset and legacy-octal-two-digits-only "do not build", because Verus's compute_only leaves char-to-integer casts such as `'a' as int` unevaluated (`clip(u32, '0') <= 48` stays stuck). Every char-literal cast in spec.rs is now the code point in hex (`'a' as int` -> `0x61`), as the specs on main already write them (clazel-base64, clazel-cookie). The meaning is unchanged; the mutation's find/replace text follows the new spelling. Locally (Verus 0.2026.10.04): 40 verified, 0 errors; 4 mutations, 4 killed by a theorem with certificates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
atiernan
temporarily deployed
to
full-verification
November 20, 2026 19:53 — with
GitHub Actions
Inactive
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the first half of Phase 7 item 7.2: the JS lexer's spec and contracts, with no implementation. Rule 3 wants the spec reviewed before code is written against it.
clazel-js-lexerstays at tier 0.Stacked on #176. Merge that PR first, or retarget this one to
mainafterwards.What's here
src/spec.rs: ECMA-262 2026's lexical grammar (§11.1, §12.2–§12.9, Annex B.1.1), written as Verusspec fns, pinned at commit0248456c.htmlflag for Annex B.1.1 that is false for modules.src/lemmas.rs: proven lemmas for the longest-element search, the trivia bounds and one-step progress.src/examples.rs: positive examples evaluated in Verus.src/contract.rsandsrc/api.rs:requires/ensuresfornext_input_elementandnext_token, stating three properties. No implementation exists yet, so they sit on a body-less trait,JsLexer, with no escape hatch.spec.rs.For the spec reviewer, first
longest_len,lex_error). A numeric literal followed by an IdentifierStart is an error, so3inand1.eare errors.ID_StartandID_Continueare left uninterpreted beyond ASCII. The implementation must tie a generated Unicode table to them, and nothing is claimed about them yet.utf16_of.identifier_early_errors_okchecks every code point, not only the escaped ones.Left out on purpose
null,trueandfalsecome back as IdentifierName.lemma_template_characters_cons, which Verus would not prove. The definition is unchanged.Verification
verification results:: 38 verified, 0 errors.cargo xtask check: STATIC CHECKS PASSED.cargo build -p clazel-js-lexer, clippy-D warningsandcargo fmt --checkare clean.cargo xtask verify --changedwas not run locally. The newvstddependency changesCargo.lock, which would make it re-check every crate. CI's full verification is the check, and its proof jobs need approval.🤖 Generated with Claude Code