run all example .hil
files as an integration test of sorts
#13
Annotations
8 warnings
build:
HILFE/Framework/Functions/TypenameFunction.cs#L9
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:
HILFE/Parsing/Expressions/FunctionDefinitionExpression.cs#L19
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:
HILFE/Framework/Functions/ParseFunction.cs#L20
'value.ValueType is not "string"' is always 'false'. Remove or refactor the condition(s) to avoid dead code.
|
build:
HILFE/Parsing/Statements/ContinueStatement.cs#L6
Type 'ContinueStatement' can be sealed because it has no subtypes in its containing assembly and is not externally visible
|
build:
HILFE/Framework/Functions/TypenameFunction.cs#L9
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:
HILFE/Parsing/Expressions/FunctionDefinitionExpression.cs#L19
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:
HILFE/Framework/Functions/ParseFunction.cs#L20
'value.ValueType is not "string"' is always 'false'. Remove or refactor the condition(s) to avoid dead code.
|
build:
HILFE/Parsing/Statements/ContinueStatement.cs#L6
Type 'ContinueStatement' can be sealed because it has no subtypes in its containing assembly and is not externally visible
|