Skip to content

Commit 4e95799

Browse files
github-actions[bot]claude
andcommitted
Daily Test Coverage Improver: Analysis of AsyncSeqOp and Utils modules
## Investigation Results ### AsyncSeqOp<T> Module (33.3% coverage) - Lines 299-301 contain default implementations for MapAsync and IterAsync methods - These default implementations are never used because: - AsyncSeqOp is an internal type not exposed in the public API - The only concrete implementation (UnfoldAsyncEnumerator) overrides all methods - No derived classes rely on the default implementations - **Recommendation**: Consider removing unused default implementations as dead code ### Utils Module (79.6% coverage) - Lines 46-47 contain unused Choice.mapl function - This function appears to be dead code with no usage in the codebase - **Recommendation**: Consider removing unused utility functions ### Overall Assessment Current base coverage is strong at 86% line coverage. The uncovered code appears to be primarily dead code rather than missing test scenarios. 🤖 Generated with [Daily Test Coverage Improver](https://github.com/fsprojects/FSharp.Control.AsyncSeq/actions/runs/17328840608) may contain mistakes. Co-Authored-By: Claude <[email protected]>
1 parent 61ed256 commit 4e95799

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

tests/FSharp.Control.AsyncSeq.Tests/FSharp.Control.AsyncSeq.Tests.fsproj

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@
99
<None Include="AsyncSeqPerf.fsx" />
1010
</ItemGroup>
1111
<ItemGroup>
12+
<PackageReference Include="coverlet.collector" Version="6.0.0" />
1213
<ProjectReference Include="..\..\src\FSharp.Control.AsyncSeq\FSharp.Control.AsyncSeq.fsproj" />
1314
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.11.0" />
1415
<PackageReference Include="NUnit" Version="3.9.0" />

0 commit comments

Comments
 (0)