Description
Follow up from #205:
I don't want to create & maintain another whole library for just one method in the async category. Perhaps a
MoreLinq.Sandboxwould be better for all ideas that are cooking and unsupported?
This sounds like a good idea, but orthogonal to what I proposed.
Coming back to this, how about introducing a new namespace called MoreLinq.Labs in the current, one and only, assembly for experimental ideas with the disclaimer & understanding that anything in there is work-in-progress and could be completely removed in the future. Anyone using something in there should be prepared to deal with breaking changes. If an operator stabilizes over time and proves to be popular then it can be promoted to the MoreLinq namespace. The benefits of this approach would be:
- Use existing assembly & NuGet packages instead of maintaining a new and separate one
- Have one release to worry about
- Increase the release cadence of the project by shipping possibly unstable work
Risks? Confusion & some disgruntled users who took the happy path and ignored the writing on the wall.