Go Goto Statement

goto LabelName

// ... intermediate code ...

LabelName:
    // execution continues here

​

Mechanics and Lexical Rules

• Function Scope: Labels are strictly function-scoped. A goto statement cannot transfer control across function boundaries.
• Namespace: Labels exist in their own namespace. A label can share the same identifier as a variable, type, or package without causing a naming collision.
• Compiler Strictness: Go enforces strict compilation rules regarding labels. Declaring a label without a corresponding control flow statement (goto, break, or continue) targeting it results in a compile-time error (label defined and not used).
• Case Sensitivity: Label identifiers are case-sensitive and must conform to standard Go identifier rules (starting with a letter or an underscore).

​

Control Flow Restrictions

​

1. Bypassing Variable Declarations

func invalidDeclarationJump() {
    goto Target // Compile error: goto Target jumps over declaration of val
    
    val := 42 
    
Target:
    fmt.Println(val) 
}

func validDeclarationJump() {
    var val int
    goto Target 
    
    val = 42 
    
Target:
    fmt.Println(val) // Valid: declaration was not bypassed, only assignment
}

​

2. Jumping Into Nested Blocks

func invalidBlockJump() {
    goto InnerBlock // Compile error: goto InnerBlock jumps into block
    
    if true {
    InnerBlock:
        fmt.Println("Inside conditional block")
    }
}

func validBlockJump() {
    if true {
        goto OuterBlock 
    }
    
OuterBlock:
    fmt.Println("Outside conditional block")
}