microsoft / microsoft/vs-threading
Non-generic AsyncLazy for lazy initialization with side effects rather than a return value
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 1k
- Forks
- 160
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 28
Description
We occasionally use AsyncLazy<object> and return null from the value factory as a means for async, thread-safe lazy initialization of objects. Defining a non-generic version of AsyncLazy would feel better than returning null from a value factory.
Contributor guide
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 existing AsyncLazy entry point and review how its generic value factory handles asynchronous, thread-safe initialization. Define the non-generic behavior for factories used only for side effects, then verify that the new API supports those call sites without returning null; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100