Repository navigation
Generate implementations from written derive headers - #2052
Draft
micahscopes wants to merge 9 commits into
Draft
micahscopes wants to merge 9 commits into
micahscopes wants to merge 9 commits into
Conversation
micahscopes
force-pushed
the
feat/written-typed-derive
branch
from
November 20, 2026 22:14
93f6266 to
ec7d5d6
Compare
This branch has not been deployed
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.
Both headers use one registration. The selected type determines the generated method signature and the constant it returns. The two implementations return 32 and 64 from
wire_code.The same preparation path supports
impl Packet with (Provider)for generated inherent methods and constants. Its provider implementsDeriveInherent.Recordfor the target it is allowed to inspect. Fe code can walk struct fields and enum payloads and use their types to build expressions or items.Code<Item>value. Templates carry the scopes of the code that wrote them. The resulting signatures and bodies undergo ordinary implementation checks.Written provider selection builds on ordinary trait-family arguments. Writing or omitting a default that produces the same trait application yields the same candidates. A selected provider still has to satisfy its declared bounds.
The standalone driver checks covered 67 cases. The example passes both applied families through the same provider, and the preparation tests cover written prerequisites and generated members across packages.