RS sayrer

Grammar and Spell Check: draft-ietf-tls-mlkem-08

Spelling / Grammar

Doubled "and and" — In both the meta-description and the Abstract: "as NamedGroups and and registers IANA values" should read "and registers". This appears twice (meta-description and section-abstract-1).
Reference inconsistency (§4.2.8) — The Introduction cites key_share Section 4.2.8 of RFC8446bis, while Section 4 and Section 4.2 cite Section 4.2.7 / 4.2.8 of plain RFC8446. Inconsistent reference target.

Reference / Citation Bugs

run a grammar and spell check on https://www.ietf.org/archive/id/draft-ietf-tls-mlkem-08.html

4:44 PM I'll fetch the draft and check it for grammar and spelling issues.

Searched the web Searched the web Issues found:

⏺ Results in. Cross-package, so benchstat can't auto-pair them, but the numbers speak clearly:

Lazy DFA vs NFA-only: same workload, different branches

BenchmarkLazyDFAHotPath — 50 shellstyle patterns, ~55 events, cache warmed:

  ┌───────────────────────┬───────────────────────┬──────┬────────┐
  │        Branch         │        sec/op         │ B/op │ allocs │
  ├───────────────────────┼───────────────────────┼──────┼────────┤

Bug Report: Clay Compiler (jckarter/clay)

Bugs found via static analysis of the Clay compiler (~38K lines of C++). All bugs are in publicly available code at https://github.com/jckarter/clay.

Bug 1 — `errno` not cleared before `strtol`/`strtod` family calls

File: literals.cpp, parseIntLiteral() and parseFloatLiteral()
Severity: Medium

OK, I've done a much more thorough examination. Let me report the bugs I found in the code as it stands in this commit, across the files it touches. Some are pre-existing but live in the same functions.

Bug 1: valid_month ignored when fields.month is provided (ECMA + Constrain path)

File: calendar_arithmetic.rs:438-481

When from_fields is called in ECMA mode with Overflow::Constrain and no explicit year, and the

	⏺ Numbers in hand:

	- iai/callgrind bench: can't run on this M1 — no valgrind on Apple
	Silicon (gungraun-runner/valgrind absent). So the instruction
	counts in the doc are inherently the AMD/Linux machine's; this M1
	can only give wall time.
	- M1 wall (v5_rotate_wall, criterion): 10.55 ms [10.52–10.59], tight.
	Was 11.63 → −8.8% on M1.
	- AMD (doc, callgrind): −30.3% instructions, −47% RAM hits, −30% est.
	cycles.


	❯ let's make a plan to install Jenkins and set up one Mac and one Linux VM as agents

	Listed 1 directory (ctrl+o to expand)

	⏺ Here's a proposed plan. A few choices need your input before we commit to specifics — I've marked them with ?.

	Decisions to lock first

	131 - for hit in self.rtree.locate_in_envelope_intersecting(&envelope) {
	132 - if self.trees[hit.data].contains(point) {
	133 - f(hit.data);
	134 - }
	135 - }
	131 + // Internal-iteration variant of `locate_in_envelope_intersecting`
	132 + // walks the R-tree on the call stack instead of pushing children onto
	133 +

	Reading the stack bottom-up: AppKit is in terminate: → _deallocHardCore:, which
	walks the global NSHashTable of windows and releases each one. During one of
	those releases, -[NSWindow dealloc] hit an NSAssert (that's what frames 0–3
	are — __assert_rtn → abort → pthread_kill). So this isn't a random segfault or
	an over-release into freed memory; it's AppKit's own invariant check firing
	inside the window teardown path on app quit. The single most useful missing
	piece is the assertion text itself. __assert_rtn writes the failing expression
	and file:line to stderr right before abort(), and the full .crash / .ips file
	usually has it in the Application Specific Information block near the top. Grab
	that — it turns this from "something's wrong during quit" into a one-line