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
Currently if I have a long function header/prototype with lots of parameters, zig fmt will force all of the parameters onto a single line.
e.g.
pub fn sgemv( order: Order, trans: Trans, m: usize, n: usize, alpha: f32, a: []const f32, lda: usize, x: []const f32, x_add: usize, beta: f32, y: []f32, y_add: usize ) void { ... }
... will be changed to:
pub fn sgemv(order: Order, trans: Trans, m: usize, n: usize, alpha: f32, a: []const f32, lda: usize, x: []const f32, x_add: usize, beta: f32, y: []f32, y_add: usize) void { ... }
The text was updated successfully, but these errors were encountered:
Add a trailing comma to the final parameter -- that should fix it.
pub fn sgemv( order: Order, trans: Trans, m: usize, n: usize, alpha: f32, a: []const f32, lda: usize, x: []const f32, x_add: usize, beta: f32, y: []f32, y_add: usize, ) void { // }
Sorry, something went wrong.
Interesting, thank you. Has it been decided that this is a mandatory style? Unsure about whether or not to close this.
I believe this style is the result of already-accepted proposals/changes. Here are some relevant issues: #1003, #2181
So I would close it unless you want to bring up a counterargument to the policy or propose an enhancement to it.
No branches or pull requests
Currently if I have a long function header/prototype with lots of parameters, zig fmt will force all of the parameters onto a single line.
e.g.
... will be changed to:
The text was updated successfully, but these errors were encountered: