Use source generators instead of reflection
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
I notice that one area where dapper can still be maybe too slow is it uses reflection to map to objects which is too slow.
I would suggest the possibility of using source generators so a person can have as fast performance as possible.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Dapper's object-mapping and reflection implementation to understand the current behavior and identify the scope of a source-generator approach. The issue does not name specific files or tests; completion would require an agreed design, preserved mapping behavior, and evidence that performance improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100