[GROOVY-11263] Analyze dead code

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 5.x
• Labels: breaking_change
• Assignee: Unassigned
• Reporter: Daniel Sun
• Created: 31/Dec/23 18:32
• Updated: 08/Jan/24 21:37

Description

As we all know, source code is meant for developers to read, and the less redundant code there is, the more developer-friendly it becomes, but Groovy allows dead code after throw, return, break and continue, e.g.

def m() {
   return
   def a = 1
}

It's better to avoid such dead code.

Issue Links

• links to: GitHub Pull Request #2023