proposal: spec: error handling with || return err

[pwtitle]

Proposal Details

I have a new error return proposal:

1. very simple, very golang, very short
2. does not add new Keyword or Operators
3. good compatibility
4. not changing the error way

** For examples: **

[pwtitle]

i like it, do you like it?

[gabyhelp]

Similar Issues

• proposal: Go 2: one line error handling with EReturn function #43644
• proposal: Go 1: Add error checking shorthand operator #58478
• proposal: Go 2: errors handling #63380
• proposal: Go 2: syntactic sugar for return fmt.Errorf #56159
• proposal: Go 2: `? :` for returning on function errors #65579
• proposal: Go 2: just return the error #56628
• proposal: Go 2: new syntax for abbreviation of `if err != nil { return ..., err }` #51146
• proposal: handle error in minimal way #57552
• proposal: Go 2: spec: simple error wrapper handling using comments #47934
• Can we simplify error handling? #38349

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[ianlancetaylor]

Looks at lot like #21161.

[ruyi789]

func test1() (b []byte,err error ){
	b, err = os.ReadFile("./test1")
	//if-simplify
	if l:=len(b);l==0||l>65536@nil,fmt.Errorf("bad data:%d",l)
	else b==[]byte("bad")@nil,fmt.Errorf("bad file:%d",l)
	else if err==io.ErrUnexpectedEOF{
		//fmt.Println(string(b))
		//panic(fmt.Errorf("ErrUnexpectedEOF:%d",l))
                return nil,err
	}
	else b,err==io.EOF@nil
	else nil,err!
    return b,nil 
}

[ianlancetaylor]

@ruyi789 That looks like a completely different idea that should be discussed on a different issue. Thanks.

[Z3NTL3]

Eyyo Rust's approach is very good and Zig's too. Very convenient, simple, elegant and compact. We need some improvement around this.

Can someone of the Go team please inform us about how far we are for a decision on how to improve this for the sake of Go.
By the way I do not like the error handling in this proposal, dont think so anyone does, again too verbose.

[pwtitle]

verbose？

|| return

verbose？？?

[ianlancetaylor]

This is very similar to #61750 and the recent #67955, with a slightly different syntax. It's syntactically unlike anything else in Go, with a return not in a block. The emoji voting is not in favor. Therefore, this is a likely decline. Leaving open for four weeks for final comments.

[ianlancetaylor]

No further comments.