Track nested-lambda closure captures during flat-expression construction #315
Annotations
12 errors and 12 warnings
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L152
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L157
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaClosureParameterUsage(int, int, int)'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L153
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.ParameterIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L152
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L157
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaClosureParameterUsage(int, int, int)'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L153
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.ParameterIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L152
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L157
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaClosureParameterUsage(int, int, int)'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L153
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.ParameterIndex'
|
|
build (ubuntu-latest):
src/FastExpressionCompiler.LightExpression/FlatExpression.cs#L152
Missing XML comment for publicly visible type or member 'LambdaClosureParameterUsage.LambdaIndex'
|
|
build (windows-latest)
The strategy configuration was canceled because "build.ubuntu-latest" failed
|
|
build (windows-latest)
The operation was canceled.
|
|
build (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L67
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L67
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L67
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L67
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L67
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (ubuntu-latest):
test/FastExpressionCompiler.IssueTests/Issue500_IndexOutOfRangeException_with_value_objects_implicit_conversions.cs#L27
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|