Repository navigation
feat(post): two problems confirmed by the spec's author, fixed in both bindings - #230
Merged
Merged
Conversation
…h bindings Short post for 26 October (morning slot): section 8.3 was a mistake, and the lazy row map is in the real code too. Both bindings now announce a batch removal while the entries exist and find a row by binary search; a hash drain at 10,000 entries went from 193 microseconds to 320 nanoseconds. Cards and captions for both platforms. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…rrection Both said section 8.3 was a deliberate trade-off. Its author wrote that it is a mistake, and that the lazy row map is in the real code too. Dated update lines link to the new post. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The spec author post takes the morning slot of 26 October. The short keeps its cards, re-dated, and becomes a planned second post at 16:00 UTC. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
The spec's author answered the spec post: section 8.3 is a mistake, not a trade-off, and the lazy row map is in the real code too. A short post reports the fixes (reflect-moc #33), and the two earlier posts carry a dated correction.
googletest-live-at-headspec-author-corrections-fixeddetect-the-leftover-copygoogletest-live-at-head(a planned double inschedule_doubles.py)cpp26-reflectionorder 40, cards and captions for LinkedIn and Facebook, card headline "193 microseconds became 320 nanoseconds" (drain per removal, hash of 10,000 entries, x86_64, binding A). The README link is pinned to the merge commit of reflect-moc feat: expand identity to "Modern C++ for production" + cluster grouping on toolset hub #33. A verbatim quote of two short phrases, no pronouns for the author.check-pubdates,check-social-renderfor both slugs,prose-lint --stricton all four posts,npm run test:prose,npm run check:future.googletest-live-at-headat 3 Nov 16:00Z (its entry is on 25 Oct, a day before its post existed), andboost-modules-1-92at 27 Oct 08:00Z (queued 26 Oct, a day early).Visual: none, because the change is text and a schedule, with the before/after in the table.
🤖 Generated with Claude Code