Process completed with exit code 1.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)

The field 'V1V2XorBenchmarks.Text' is assigned but its value is never used

Nullability in constraints for type parameter 'TState' of method 'RawConsoleLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.

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.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.