We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In many places Zeek allows trailing commas. This seems to be handled inconsistently.
For enums I see expected behavior:
type E: enum { a, b, c, };
For set-like constructs I see an additional space:
const s = { 1, 2, 3, }; # ^ const r: RecordType = [ $a=1, $b=2, $c=3, ]; # ^
We probably have the same issue for function-like constructors, e.g.,
const a = vector(1, 2, 3, ); # ^
The issue seems to be that we insert an space after , in the contexts even though it is not followed by more arguments.
,
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In many places Zeek allows trailing commas. This seems to be handled inconsistently.
For enums I see expected behavior:
For set-like constructs I see an additional space:
We probably have the same issue for function-like constructors, e.g.,
The issue seems to be that we insert an space after
,
in the contexts even though it is not followed by more arguments.The text was updated successfully, but these errors were encountered: