Repository navigation
Conversation
The tape reader's Endless input, which kept 0.16's inflate off a bug in a stream cut short, is gone: 0.17's inflate checks the bits it has before tossing them, so a fixed reader does, and a cut-short stream reads as corrupt. The readme and the plugin guide say Zig 0.17.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/zig-0.17/ re-ran zig fmt's upgrades and the one-answer renames after each merge from main. It goes in the last PR before zig/0.17 reaches main, as its header said; a later merge would find it in history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Folded into zig/0.17 directly, as the last commit before the switch, together with the final merge of main (to #555). |
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
1 participant
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.
Part of fizzyedit/plans#5 (
plans/ZIG_0_17_PLAN.md, step 2): the last PR beforezig/0.17goes tomain. Stacked on #505.What changes
scripts/zig-0.17/is deleted (rewrite.sh,fields.py,unused.py). It re-ranzig fmt's upgrades and the one-answer renames over the code each merge frommainbrought, and its header said it goes in the PR that merges the branch. Ifmainmoves before the switch, the catch-up can run it from history.check-examples.sh's note now gives the real order: it stays on the examples'zig-0.17branches until their PRs (zig: build on Zig 0.17 example-app#8, zig: build on Zig 0.17 example-plugin#13) land just after the switch, then flips tomainin a PR of its own.Merge it only when nothing more is coming from
mainbefore the switch.SDK impact
Verified
.md,.zig,.sh,.yml);bash -n scripts/check-examples.sh.🤖 Generated with Claude Code