Copy with nested pointer to struct causes panic about copier HOT 7 CLOSED

@qzyse2017 Can't agree, it's just a temporary solution. What if we have 300 nested field? It should be handled inside the library, if the nested field is nil, then reflect.New with the type of the field.

from copier.

Possible it's trying to call the reflectValue.Elem() on a nil reflect.Value, so it won't have an exact Elem(). But correct me if I'm not right.

from copier.

@sudo-suhas have you found any fix for this?

from copier.

No.

from copier.

b.nested = &nested{}

initialize the pointer can avoid panic.

https://play.golang.org/p/o4m2S_pqJPH

from copier.

Hey. Any update on this? Is fix coming to the library?

from copier.

This example uses unexported anonymous fields. Unexported fields cannot be copied to.
PR #72 adds support for exported anonymous fields and avoid panic in case of anonymous fields.

from copier.