Use Castle to generate delegate proxies #537
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently @stakx did a favor to all of us and added possibility to generate delegate proxies to the Castle.Core library. Simplified our internal logic to use the Castle.Core generator for both delegates and classes.
Notice, I haven't removed the deprecated classes we already have, as it's not allowed by SemVer I'm trying to follow 😉 Instead, just deprecated all the types to remove them in future.
@dtchepak Please review the PR and let me know if you are fine. Don't merge it yet - I want to spend some time and benchmark the performance (after #536 is merged). Created it early, so we can discuss the approach 😉
UPD:
According to the benchmark results the activation performance is comparable: