Skip to content

Change explicit implementation method naming scheme to prevent name collisions#471

Merged
stakx merged 5 commits intocastleproject:masterfrom
stakx:method-name-collision
Aug 23, 2019
Merged

Change explicit implementation method naming scheme to prevent name collisions#471
stakx merged 5 commits intocastleproject:masterfrom
stakx:method-name-collision

Conversation

@stakx
Copy link
Copy Markdown
Member

@stakx stakx commented Aug 23, 2019

Fixes #469.

stakx added 5 commits August 23, 2019 14:42
When deciding how to name interface methods on the proxy type, Dynamic-
Proxy attempts to prevent name collisions by switching to explicit
implementation (where method names get prefixed with the declaring
type's name).

As this test shows, this strategy is not sufficient to prevent name
collisions, because the namespace does not get included in type names.
@stakx stakx merged commit e2dfb57 into castleproject:master Aug 23, 2019
@stakx stakx deleted the method-name-collision branch August 23, 2019 15:45
@jonorossi jonorossi added this to the v4.4.1 milestone May 6, 2020
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.

"Duplicate element: MetaMethod" for specific combinations of namespace & type names

2 participants