Panic when private fields differ about pretty

[cee-dub]

Thanks for the report, especially the simple code to reproduce. I'll see if I can take a look at this, unless you have started on a fix already?

[dgouldin]

I don't have a fix, but my suggestion would probably be to call out the field that differs but not compute the diff itself when the field is private.

[cee-dub]

I looked into this last night, but I had some degree of trouble deciphering the output from diff_test.go after making some changes in an attempt to fix the problem.

Your suggestion makes some sense, but it doesn't really address the use case of someone trying to determine how the values are actually different. I think that limits its utility (granted, it's better than a panic!).

I don't have more time in my schedule to look at it this week, unfortunately. If I had the time, I would start by updating the tests to cover your case (use a struct that has typed private fields, not just interface{} fields, including some as pointers) and also consider updating the test helpers to make it easier to decipher the failure messages. With that, the changes in diff.go should be fairly straightforward.

On Jan 27, 2015, at 19:37, David Gouldin [email protected] wrote:

I don't have a fix, but my suggestion would probably be to call out the field that differs but not compute the diff itself when the field is private.

—
Reply to this email directly or view it on GitHub.