You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use the most recent version of the Checker Framework in my project.
After the bump an error has been thrown.
The code looks good to me, so I assume it is / could be a regression in the Checker Framework.
The framework does not complain using 2.1.5 and 2.1.6
After switching to 2.1.7 it complains:
Demo.java:20: error: [lambda.param.type.incompatible] incompatible parameter types in lambda expression.
.map(key -> String.format("%s=%s", key, timeTemperatures.get(key))).collect(Collectors.joining(",")));
^
found : @KeyFor("this.timeTemperatures") DayOfWeek
required: @KeyFor("[error for expression: this.timeTemperatures error: this.timeTemperatures: findPackage threw an exception when looking up package this: null]") DayOfWeek
1 error
error: [[all, keyfor]:lambda.param.type.incompatible] incompatible parameter types in lambda expression.
for the respective function it does not complain anymore, but I don't think suppress warnings is the correct way to solve it (perhaps only a temporary workaround).
I can't reproduce these errors any more. I believe they were fixed by two recent changes:
the SOE was fixed by: aff0922 and the "expression.unparsable.type.invalid" was fixed by 8ce6ee5.
Previously reported here: https://groups.google.com/d/msg/checker-framework-discuss/v9k0y6cRmyE/2GfHd_iGCQAJ
Hi,
I would like to use the most recent version of the Checker Framework in my project.
After the bump an error has been thrown.
The code looks good to me, so I assume it is / could be a regression in the Checker Framework.
The framework does not complain using 2.1.5 and 2.1.6
After switching to 2.1.7 it complains:
error: [[all, keyfor]:lambda.param.type.incompatible] incompatible parameter types in lambda expression.
After using
for the respective function it complains about:
After using
for the respective function it does not complain anymore, but I don't think suppress warnings is the correct way to solve it (perhaps only a temporary workaround).
Here the code that raises the error:
I receive another error using 2.1.7 and a static method
The text was updated successfully, but these errors were encountered: