I can see several reasons: You are calling a function that returns a #[must_use] type, but in your specific case, you know you can safely ignore the value. It is possible to use a _ pattern for that (which is not a variable binding, it’s a pattern of its own, but this is probably where … Read more
Yes, you can silence pylint warnings. Here is one way: import say def f(a): # pylint: disable=unused-argument return say.fmt(“The value of ‘a’ is {a}”) Alternatively, you can create a config file and add these lines to it: [MESSAGES CONTROL] disable=unused-argument Reference: https://pylint.readthedocs.io/en/latest/faq.html#is-it-possible-to-locally-disable-a-particular-message https://pylint.readthedocs.io/en/latest/user_guide/run.html#command-line-options
I was having the same problem. Using say express and routing you would often only want the res parameter. router.get(“https://stackoverflow.com/”, function (req, res) { res.end(‘Bye.’); }); Your idea of using _ works here, but I’ve also found doing this works too. function (_1, _2, _3, onlyThis) { console.log(onlyThis); } This seems better, as only doing … Read more
There are two separate warnings. One says the field was never assigned a value, which is the one you have disabled. The other says the field was never used, which is the warning you are getting. Add Inject to settings -> editor -> inspections -> java -> declaration redundancy -> unused declarations -> entry points … Read more
You can just omit the parameter names: int main(int, char *[]) { return 0; } And in the case of main, you can even omit the parameters altogether: int main() { // no return implies return 0; } See “§ 3.6 Start and Termination” in the C++11 Standard.
Just so we have an example to work from, this is fairly common with jQuery’s $.each where you’re writing code that doesn’t need the index, just the value, in the iteration callback and you’re using this (which jQuery also sets to the value) for something else: $.each(objectOrArrayLikeThing, (_, value) => { // Use `value` here … Read more
I’m unsure if it’s still supported in the new LLVM compiler, but GCC has an “unused” attribute you can use to suppress that warning: BOOL saved __attribute__((unused)) = [moc save:&error]; Alternatively (in case LLVM doesn’t support the above), you could split the variable declaration into a separate line, guaranteeing that the variable would be “used” … Read more
With the @Suppress annotation You can suppress any diagnostics on any declaration or expression. Examples: Suppress warning on parameter: fun foo(a: Int, @Suppress(“UNUSED_PARAMETER”) b: Int) = a Suppress all UNUSED_PARAMETER warnings inside declaration @Suppress(“UNUSED_PARAMETER”) fun foo(a: Int, b: Int) { fun bar(c: Int) {} } @Suppress(“UNUSED_PARAMETER”) class Baz { fun foo(a: Int, b: Int) { … Read more