proposal: Go 2: Error-Handling Paradigm with !err Grammar Sugar

[xiaokentrl]

Hi, if you like this idea please give a heart emoji to me, Thank you very much

package main
 
import (
    "fmt"
    "os"
)
 
func main() {
	/*
	func demo(){
	    file, err := os.Create("example.txt") 
	    if err != nil {
	        return nil, err
	    }
	    defer file.Close()
	}
	*/

	func demo_1(){
	    file, e := os.Create("example.txt") e(nil,e)        // == return nil, err
	    defer file.Close()
	}
                          
	func demo_2(){
	    file, e(nil,e) := os.Create("example.txt")        // == return nil, err
	    defer file.Close()
	}

	func demo_3(){
	    Try
	        file, err  := os.Create("example.txt")
		defer file.Close()
	    Catch {
	        return nil, err
	    }
	}


	//file, e := os.Create("example.txt")  e(nil,err)
	//file, e := os.Create("example.txt")  e(panic)
	//file, e := os.Create("example.txt")  e("funcName")

	//file, e.panic := os.Create("example.txt")
	//file, e.call( "funcName") := os.Create("example.txt")

	//e.nil
	//e.Info
	//e.IsNumber
	
	//if ( e.nil )
	//if ( e.IsNumber )

	if dd, e := demo_1(); e.nil{
            fmt.Printf( "success dd" )
            return
	}
	fmt.Printf( "fail", e.info )
}

[xiaokentrl]

If the Go compiler encounters the function e( ), it automatically appends the following code on the next line:

if err != nil { 
    return nil, err
}

[ianlancetaylor]

I'm sorry, I don't understand the actual proposal here. What are the Try and Catch lines in demo_3?

[thediveo]

(somehow Go2 error proposals seem to be like singing talent contests)

[cyberbeast]

I am not sure I understand the semantics of the proposal from the example provided. The syntactic sugar is too cryptic.

[Sniperq2]

If the Go compiler encounters the function e( ), it automatically appends the following code on the next line:

if err != nil { 
    return nil, err
}

Are you about typing lot's of boilerplate code like this? Modern IDEs already has live templates/code snippets. Also you can create you own snippets for your errors. Is this acceptable to you?

[xiaokentrl]

I'm sorry, I don't understand the actual proposal here. What are the Try and Catch lines in demo_3?

Hi, if you like this idea please give a heart emoji to me, Thank you very much

package main
 
import (
    "fmt"
    "os"
)
 
func main() {
	/*
	func demo(){
	    file, err := os.Create("example.txt") 
	    if err != nil {
	        return nil, err
	    }
	    defer file.Close()
	}
	*/

	func demo_1(){
	    file := os.Create("example.txt").checkError( return , nil , err )
	    defer file.Close()
	}
                          
	func demo_2(){
	    file := os.Create("example.txt").checkError( panic )
	    defer file.Close()
	}

	func demo_3(){
	    file := os.Create("example.txt").checkError( return , func(){
                return 2 + 3 , nil
            })
	    defer file.Close()
	}

	if dd := demo_1(); dd.hasError {
            fmt.Printf( "dd  hasError" )
            return
	}
	fmt.Printf( "dd" )
}

[thediveo]

This example is even more confusing, I don't understand it at all. Please write down a proper proposal detailing what the syntax is and how the compiler transforms it. Thank you.

[xiaokentrl]

This example is even more confusing, I don't understand it at all. Please write down a proper proposal detailing what the syntax is and how the compiler transforms it. Thank you.

Do you understand this? Thank you
#63647

[xiaokentrl]

This example is even more confusing, I don't understand it at all. Please write down a proper proposal detailing what the syntax is and how the compiler transforms it. Thank you.

	func demo_1(){
	    file := os.Create("example.txt").checkError( return , nil , err )     
	    defer file.Close()
            
           //   when【 .checkError( )   】 appears，auto append    file , err := os.Create("example.txt")
           //   when【 .checkError( return , nil , err )   】 appears，auto append  if err != nil 

	}

[thediveo]

This example is even more confusing, I don't understand it at all. Please write down a proper proposal detailing what the syntax is and how the compiler transforms it. Thank you.

Do you understand this? Thank you #63647

not either, looks like a dump, but not like a fleshed-out proposal, there are good examples of issues that actually are easy to follow along and that give a concise picture. linking to the confusing issue opening itself doesn’t help.

[findleyr]

It doesn't look like there's a concrete proposal here, and based on the emoji voting this is likely decline. Leaving open for four weeks for additional comments.

[adonovan]

There were no further comments.