-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reflect: potential change required in DeepEqual #37897
Comments
After reading a bit more about function comparison, which does not seem very obvious, may be we could just parameterize the DeepEqual call so that this check can be disabled ? Just wondering ... |
Per https://golang.org/ref/spec#Comparison_operators:
And per the
Any change to that behavior would violate the Go 1 compatibility policy. |
Sorry, we aren't going to make this change in |
@ianlancetaylor @bcmills many thanks for this feedback, I fully understand.Many thanks again |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
See issue # 11059 in Terraform AWS Provider
and more specifically this part
DeepEqual fails because of the following item which is however perfectly identical in both cases:
What did you expect to see?
If pointer addresses are identical
true
should be returned so something like:might be better (IMHO)
What did you see instead?
DeepEqual returns false
The text was updated successfully, but these errors were encountered: