[jira] [Created] (GROOVY-8643) Make for-in null safe for CompileStatic

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Created] (GROOVY-8643) Make for-in null safe for CompileStatic

JIRA jira@apache.org
Sergiy created GROOVY-8643:

             Summary: Make for-in null safe for CompileStatic
                 Key: GROOVY-8643
                 URL: https://issues.apache.org/jira/browse/GROOVY-8643
             Project: Groovy
          Issue Type: Bug
          Components: Static compilation
    Affects Versions: 3.x, 2.4.x
            Reporter: Sergiy

See following simple script:
import groovy.transform.CompileStatic;

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

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?


This message was sent by Atlassian JIRA