[GROOVY-8643] Make for-in null safe for CompileStatic

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.0.4, 2.5.19, 3.0.13
• Component/s: Static compilation
• Assignee: Eric Milles
• Reporter: Sergiy
• Created: 14/Jun/18 07:53
• Updated: 30/Jul/22 23:31
• Resolved: 12/Jul/22 20:13

Description

See following simple script:

import groovy.transform.CompileStatic;

@CompileStatic
void printList(List l){
    println "List:"
    for (Object o in l) {println o}
    println "Done"
}

printList(null)

It crashes with null pointer exception due to list being null in the for loop. However it works perfectly fine when CompileStatic annotation is removed. I believe this inconsistency is a bug as the whole point of introducing a new for-in construct in groovy appeared to be to make it a null safe construct (unlike for (Object o: l) construct in java). However, when compiling statically, it seems to be compiled as the java iterator it replaces, breaking away from groovy convention without even a warning.

Any chance to have it fixed in 3.x?