Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Keep unknown and excluded fields untouched
This fallback runs precisely when
nmdid not match an allowed field. For a mutable type with onlyvalue::Intanddefaults(T) = (value=10, extra=20),applyfield!(f, x, :extra)now throws becauseextrais not a field; it previously returned false.constructfromalso fails because it merges defaults before calling this dispatcher. For an excludedvaluewith constructor value 42 and default 10, this block overwrites the value with 10 while returning false. The documented API skips unknown/excluded fields and returns whether the callback ran. Please remove the invalid block fromapplyfieldwithout adding it here, and cover both cases.AI disclosure: This work was prepared with assistance from OpenAI Codex.