docs: add Coming-from-Python section + fix stale counts - #1
Conversation
Adds a "Coming from Python" on-ramp table (verified against the repo's own examples/ and tests) and corrects suite/test-count accuracy issues. Co-Authored-By: Claude <noreply@anthropic.com>
|
🤖 Independent Claude review: Ready. Verified: all 6 Mojo snippets in the Coming-from-Python table check out against
No invented APIs. Python-side Count re-verified by counting test fns via API: test_date 11 + test_feed 19 + test_real_feed 10 + test_xml_parser 30 = 70, matching README ('70 tests across four files … XML tokenizer (30)'). 'Eleven pure-Mojo libraries' and the mojo-xml cross-links are present. The diff itself only adds the table (the accuracy items were already correct upstream, as the PR body notes). |
|
Docs review (sonnet): SHIP-WITH-NITS The 5-row Nit: the title/description says "fix stale counts," but nothing was stale — the diff is a pure +12/-0 addition with zero count changes. Title overstates what the PR does; trim before merge (harmless). |
Summary
Two documentation changes:
the intro) mapping the familiar Python API to this library's real API.
Every snippet was extracted from this repo's own
examples/andtest/;nothing was invented.
Test counts were re-verified by actually counting the test functions in the
repo (not trusting the prior text).
From an automated review (personal-context#62); drafted by Claude Code — please review the Coming-from-Python snippets for API accuracy.