build.gradle file, task using << notation, intellij warns: "Cannot infer argument type"

Question

I'm new to groovy and gradle and was wondering whether someone knew why my scriplet wasn't working (edit actually it does work but the warning still appears). This section is taken out of the build.gradle script and intellij highlights this and complains that it: "Cannot infer argument types". any help would be nice :)

task hellofun << {
    [silly:'billy'].each { k, v ->
        println "$k=$v"
    }
}

EDIT: I have submitted a bug request informing Intellij of this problem

EDIT: apparently this is a known bug I'll update this once the bug is fixed

That's odd. Your code works flawlessly for me. What version of Gradle are you using? Will the task fail, or is the problem just that intellij is complaining about it? — silverbeak, Dec 12 '13 at 08:36
huh... it also works for me but intellij complains about it. — coderatchet, Dec 12 '13 at 19:50
Which version of IntelliJ? Can't reproduce in IntelliJ 13. (IntelliJ 12 has very limited Gradle support.) In any case, it's just a warning, and I don't know what you mean by "my scriplet wasn't working". — Peter Niederwieser, Dec 13 '13 at 07:36
it is definitely intellij 13. version IU-133.193 to be precise — coderatchet, Dec 13 '13 at 13:10

score 10 · Accepted Answer · answered Jul 17 '15 at 02:28

10

If you are willing to disable the Groovy > Assignment Issues > Incompatible type assignments inspection, the warning goes away.

answered Jul 17 '15 at 02:28

pmcollins

164
1
3

19

ah yes, sweep the problem under carpet. – coderatchet May 20 '19 at 23:21

coderatchet · Answer 2 · 2014-05-25T05:55:42.403

In a highly dynamically typed language such as groovy where names and symbols are resolved in arbitrary ways It would be quite difficult to determine the validity of any statement ahead of time without running the program. even running the program would theoretically not divulge all possible permutations of input that may change the runtime validity of a statement.

I applaud intellij's attempt at this hard problem and can live with a few incorrect syntax warnings here and there.

score 2 · Answer 3 · answered Sep 07 '14 at 09:07

2

Untill the IntelliJ bug is fixed, there is a workaround: use doFirst instead of <<.

task hellofun() {
  doFirst {
    [silly:'billy'].each { k, v ->
      println "$k=$v"
    }
  }
}

Thanks for submitting the bug :)

answered Sep 07 '14 at 09:07

Odinodin

2,147
3
25
43

2

This is not a workaround. You should avoid << since many people confuse configuration (){ with execution ()<<{ – Jocce Nilsson Oct 17 '14 at 09:15

score 1 · Answer 4 · answered Jul 21 '16 at 15:51

1

For the workaround, you should really call was was indicated by the << (doLast)

 task hellofun() {
   doLast {
     [silly:'billy'].each { k, v ->
       println "$k=$v"
     }
   }
 }

answered Jul 21 '16 at 15:51

Steven Spungin

27,002
5
88
78

score 0 · Answer 5 · answered Jul 31 '19 at 08:53

0

In Intelij press Double shift (search all) enter "Assignment Issues" and change Assignment Issues: Incompatible type assignments inspection to "OFF"

answered Jul 31 '19 at 08:53

HolyM

301
3
9

build.gradle file, task using << notation, intellij warns: "Cannot infer argument type"

5 Answers5

Linked