Add aggressive inlining support for generated mapping methods #2101
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.
Add aggressive inlining support for generated mapping methods
Description
This pull request adds support for applying
MethodImplOptions.AggressiveInliningto generated mapping methods, allowing users to optimize performance based on their specific needs.Key changes:
AggressiveInliningTypesenum withNone,ValueTypes,ReferenceTypes, andAlloptionsAggressiveInliningTypesproperty toMapperAttributefor configuration[MethodImpl(MethodImplOptions.AggressiveInlining)]attributeTechnical details:
The implementation introduces a new configuration option that allows users to control when aggressive inlining should be applied to generated mapping methods. This is particularly useful for performance-critical scenarios where the overhead of method calls can be significant.
The feature supports granular control:
None: No aggressive inlining (default, maintains backward compatibility)ValueTypes: Apply to struct mappings onlyReferenceTypes: Apply to class mappings onlyAll: Apply to all mappingsExample usage:
Performance impact:
This feature allows users to achieve better performance in scenarios where mapping methods are called frequently, especially for simple mappings where the method call overhead is significant compared to the mapping logic itself.
Checklist
Related Issues
#1384