linksplatform / linksplatform/Data.Doublets
Add benchmarks to compare nullable handler and non-nullable handler
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Create the function that gets the handler and checks is it null or default.
- [ ] If the handler is null - return Continue constant. Otherwise call the handler.
- [ ] If the handler is the default handler - return Continue constant. Otherwise call the handler.
- [ ] Pass null
- [ ] Pass the default handler
- [ ] Create the function that gets the handler and checks is it null.
- [ ] If the handler is null - return Continue constant. Otherwise call the handler.
- [ ] Pass null
- [ ] Pass the default handler
- [ ] Create the function that gets the handler and just calls the handler
- [ ] If the handler is the default handler - return Continue constant. Otherwise call the handler.
- [ ] Pass the default handler
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 locating the nullable and non-nullable handler implementations and the repository's existing benchmark setup. Add benchmark cases for the listed null, default-handler, and direct-call scenarios, then run the relevant benchmark command. Done means all requested comparisons are represented and produce results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100