tree 665edc6d6efa7416baba1daa03dfb819c41da76a
parent 1776240f8f841dfa00cb72d811301dbb0298f983
author Joe Tsai <joetsai@digital-static.net> 1591659451 -0700
committer GitHub <noreply@github.com> 1591659451 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJe3su7CRBK7hj4Ov3rIwAAdHIIAC5I5Y84ExVUQ7LZ3BZ5L9Bm
 Zhv5Gcxd5FwDUEQoYyGwQptkOBGwi8FdTMZGBDLcZxd6Ynoz7RI9lrruCkQk3UhW
 vDzajsWFlrbtmBej4XPXcS9R6txYNsJL9i/Zk7dtAZs5bqjgA3pGiWmKBQPqdsTR
 3RqaKLIz1Iwos8h3L60NaV9Di35puXVzHGU7+/K1mWo9bAVhntjifi301q6GCI11
 YrY5YNFW/c3OebqJp+5LlfxROzc2Wz9Rq7IUcghslg/8esKxDgg2+NNyXWy9xXhi
 vGPjyfsZzOXFJ8aUpkJhr/B63tCMkyQicCCSBUX5NpzpQoWL1Bx7aBa4e3YffP4=
 =AqKH
 -----END PGP SIGNATURE-----
 

Avoid leaking implementation details of the exporter (#206)

The current implementation for forcibly exporting fields relies on
the reflect.Value.Addr method for the parent struct value,
where it copies a non-addressable struct onto to the heap so
that it is addressable. However, this action leaks a subtle detail
of how the internal implementation works since the accessed field
for within a struct is only addressable if and only if the
parent struct is also addressable.

Modify the implementation to avoid leaking this implementation detail
by shallow copying the accessed unexported field to remove any
notion of addressability if the parent struct is also unaddressable.

Fixes #181