Bugfix - Go 1.6 reflect embedded unexported field access #10
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.
This fixes an incompatibility introduced in Go 1.6.
This PR updates the reflective struct walking in the
reflectValue()
method to check if a field is not anonymous before skipping it, making sure that we don't skip validly accessible (exported) embedded values in an unexported field.This new checking logic is the new recommended strategy for reflective struct walking as of the Go 1.6 release.
Related/References:
(reflect: resolve incompatibility between gc and gccgo for unexported embedded structs golang/go#12367)
(https://go-review.googlesource.com/#/c/14085/)