Repository navigation
Conversation
marcusw0
force-pushed
the
feat/optional-capture-hover
branch
from
October 19, 2026 22:40
c9f3372 to
79bb9b2
Compare
marcusw0
force-pushed
the
feat/optional-capture-hover
branch
from
October 20, 2026 22:54
79bb9b2 to
2b90e72
Compare
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.
Adds explanations below the existing hover signature and type info for the following:
Also has separate explanations for value captures and reference captures.
Refs #1174
Validation:
zig build test -Dtest-filter=hover --summary allandzig build test --summary allzig build -Doptimize=ReleaseSafeand using in my editorThe referenced issue has a broad idea for features like this. I'm not sure if this covers closing it, but I can keep working on more of these additions if not.