Vectorized ROT-47 cipher #6
Merged
Annotations
15 warnings
|
Build:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L41
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L96
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/Science.Cryptography.Ciphers/Tools/TabulaRecta.cs#L38
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/Science.Cryptography.Ciphers.Specialized/Encodings/HexEncoder.cs#L55
Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)
|
|
Build:
perf/Science.Cryptography.Ciphers.Benchmarks/v1v2/XorBenchmarks.cs#L16
The field 'V1V2XorBenchmarks.Text' is assigned but its value is never used
|
|
Build:
src/Science.Cryptography.Ciphers.Console/RawConsoleLogger.cs#L8
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.
|
|
Build:
src/Science.Cryptography.Ciphers.Console/Program.cs#L224
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.
|
|
Build:
src/Science.Cryptography.Ciphers.Console/Program.cs#L489
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.
|
|
Build:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L41
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L96
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Benchmark:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L41
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Benchmark:
src/Science.Cryptography.Ciphers/Extensions/ValueEnumerableExtensions.cs#L96
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Benchmark:
src/Science.Cryptography.Ciphers/Tools/TabulaRecta.cs#L38
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Benchmark:
src/Science.Cryptography.Ciphers.Specialized/Encodings/HexEncoder.cs#L55
Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)
|
|
Benchmark:
perf/Science.Cryptography.Ciphers.Benchmarks/v1v2/XorBenchmarks.cs#L16
The field 'V1V2XorBenchmarks.Text' is assigned but its value is never used
|
Loading