Skip to content

Fix Equals and GetHashCode override check for proxy generation hooks having multiple Equals methods - #721

Merged
stakx merged 4 commits into
castleproject:masterfrom
stakx:bugfix/proxy-generation-hook-record-classes
Jan 1, 2026
Merged

Fix Equals and GetHashCode override check for proxy generation hooks having multiple Equals methods#721
stakx merged 4 commits into
castleproject:masterfrom
stakx:bugfix/proxy-generation-hook-record-classes

Conversation

@stakx

@stakx stakx commented Jan 1, 2026

Copy link
Copy Markdown
Member

Fixes #720.

I am not adding a recommendation for implementing IProxyGenerationHook as record classes in this PR. Such a recommendation should perhaps entail turning AllMethodsHook into a record class too, which could be a small breaking change. Better to look into that separately.

@stakx stakx added this to the v6.0.0 milestone Jan 1, 2026
@stakx stakx self-assigned this Jan 1, 2026
@stakx
stakx force-pushed the bugfix/proxy-generation-hook-record-classes branch from 20bbad2 to 5f32f34 Compare January 1, 2026 23:37
@stakx stakx changed the title Fix Equals and GetHashCode override check for proxy generation hooks that have two Equals methods due to implementing IEquatable<> Fix Equals and GetHashCode override check for proxy generation hooks having multiple Equals methods Jan 1, 2026
@stakx
stakx merged commit bf0297a into castleproject:master Jan 1, 2026
4 checks passed
@stakx
stakx deleted the bugfix/proxy-generation-hook-record-classes branch January 1, 2026 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AmbiguousMatchException when using a proxy generation hook that is implemented as a record class

1 participant