Fix ast.metal_kernel typo in the custom Metal kernels guide - #3997
Merged
zcbenz merged 1 commit intoAug 5, 2026
Merged
Conversation
zcbenz
approved these changes
Aug 5, 2026
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.
Proposed changes
The custom Metal kernels guide refers to
ast.metal_kernel.__call__, which does not exist, so the link is dead:Looks like a typo for
fast.metal_kernel, which is how the same page refers to it in five other places.While fixing the name I also adjusted the wording, because
verboseis not an argument tofast.metal_kernelitself. It is passed when calling the kernel thatmetal_kernelreturns, which is what the example further up the page does:So the sentence now says "when calling the kernel returned by :func:
fast.metal_kernel" rather than pointing at the factory function.Checklist
Put an
xin the boxes that apply.pre-commit run --all-filesto format my code / installed pre-commit prior to committing changes(docs only; the page now builds with no unresolved references)
small disclosure, same as my other PRs: freshman contributor and Claude Code helps me sweep, but i built the docs in nitpick mode to find this, then checked the metal_kernel docstring to confirm where
verboseactually belongs before rewording rather than just swapping the typo.