DapperLib / DapperLib/DapperAOT
Adding benchmarks to the documentation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 472
- Forks
- 43
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 18
Description
First of all, Thank you very very much @mgravell for your hugely-appreciated efforts.
.NET would not be the same without you.
This library is very great and very important, and I can not stop introducing my friends and colleagues to it.
I would just suggest adding benchmarks to the documentation to show how important this library is.
It will be the easiest way for people to understand its importance by seeing how faster and less memory this approach provides.
Thank you a lot again
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
The issue names no files, tests, or entry points; start by locating the documentation and any benchmark entry point in DapperAOT. Done means the documentation contains reproducible performance and memory benchmark results that demonstrate the approach's benefit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100