-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
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
Ban // autofix
in linter
#10491
Ban // autofix
in linter
#10491
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great. autofix is an indication of forgetting something, be it using the variable or intentionally ignoring it.
@@ -3184,8 +3172,7 @@ pub const FileSink = struct { | |||
return .{ .result = {} }; | |||
} | |||
|
|||
pub fn flushFromJS(this: *FileSink, globalThis: *JSGlobalObject, wait: bool) JSC.Maybe(JSValue) { | |||
_ = wait; // autofix | |||
pub fn flushFromJS(this: *FileSink, globalThis: *JSGlobalObject, _: bool) JSC.Maybe(JSValue) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think unused parameters should keep the variable name if comptime logic requires them. Makes it a little more clear what it would be used for. Otherwise the parameter should be completely removed from the function signature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah
What does this PR do?
Ban
// autofix
in linterIt is very lazy to commit
// autofix
commentsHow did you verify your code works?