OK, I agree, this should not be a warning.

This can be reproduced with a simpler use case:

import java.util.Map;

public class LambdaWarning {
    void foo() {
        Map.of("foo", "bar").forEach((key, value) -> {
			System.out.println(key);
		});
    }
}

So you have several ways to fix that for now:

use a quick fix to ignore this compiler problem:

If your project already contains a .settings/org.eclipse.jdt.core.prefs file, it will update it. If not, it will make the config change not portable, hidden deep inside something like

{Path to VS Code metadata}/User/workspaceStorage/{some hash}/redhat.java/jdt_ws/.metadata/.plugins/org.eclipse.core.resources/.projects/{foldername_somehash}/.settings/org.eclipse.jdt.core.prefs

define an Eclipse preferences file, say .vscode/java.prefs (but you can choose any name/location), and add:

org.eclipse.jdt.core.compiler.problem.unusedLambdaParameter=ignore

Then reference this file in your vscode settings, e.g. .vscode/settings.json:

"java.settings.url": ".vscode/java.prefs"

Anyways, we'll disable that warning by default for the next release.

It should not warn "The value of the lambda parameter query is not used ." #4216

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions