Pass setval calls through SubstructureField to the contained Structure #31
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.
(If the value is a Structure, then replace the contained one.)
Currently, setting to a SubstructureField directly will replace the field with whatever you set, which can break the parent structure if what you set isn't a BaseField type.
With this change,
name.first = 'bob'
will callsetval
on thePascalString16
structure undername.first
. This might not be a meaningful operation for many Structure types, but at least it will now raise an exception if setval hasn't been defined.