The type or namespace name 'Yielders' does not exist in the namespace 'Tenekon.Coroutines.Iterators' (are you missing an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'Nothing' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'ManualResetCoroutineCompletionSource<>' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'Nothing' could not be found (are you missing a using directive or an assembly reference?)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

'Range.GetOffsetAndLength(int)' does not need a CLSCompliant attribute because the assembly does not have a CLSCompliant attribute

'Range.GetOffsetAndLength(int)' does not need a CLSCompliant attribute because the assembly does not have a CLSCompliant attribute

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.

This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.