[GROOVY-8472] Final variable analysis doesn't account for early exit for try/catch/finally

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0-rc-2
• Assignee: Paul King
• Reporter: Paul King
• Created: 07/Feb/18 00:24
• Updated: 26/Jul/18 04:38
• Resolved: 30/Apr/18 08:27

Description

An example with early return from a method:

def method(String foo) {
    final str
    try {
        str = foo.trim()
    }
    catch(e) {
        println e
        return null
    }
    int exitCode = str.isInteger() ? str.toInteger() : null
    exitCode
    //str.isInteger() ? str.toInteger() : null // this doesn't trigger the error
}

println method(null)

And a slight rearrangement of above:

def method(String foo) {
    final str
    try {
        return foo.trim()
    }
    catch(e) {
        str = '-1'
    }
    int exitCode = str.toInteger() // The variable [str] may be uninitialized
    exitCode
}

println method(null)

Issue Links

• is cloned by: GROOVY-8552 Final variable analysis doesn't account for early exit for while loop