proposal: Go 2: add ? or ?() to the golang to handle the err return

[yangyile1990]

Proposal Details

func exampleFunction() (any, error){
    res, err := run()
    err ? return nil, err

    num, err := calc()
    err ? return nil, errors.Errorf("calc is wrong. error is:%v", err)

    // if the err need more than one line to handle
    val, err := get()
    if err != nil {
        do1()
        do2()
        return nil, err
    }

    //or can use this( may be no need to add this):
    err ? {
        do1()
        do2()
        return nil, err
    }
}

The ? can be ? or ?-> or ?! or some other symbol not using in golang before.

The ? can means if anything != nil ...

you can also add ?() to handle err return.

for example:

func exampleFunction() (any, error){
    res, err := run()
    err ?(nil, err) // means if err != nil return nil, err

    num, err := calc()
    err ?(nil, errors.Errorf("calc is wrong. error is:%v", err)) // means if err != nil return nil, errors.Errorf(balabala)

    // if the err need more than one line to handle
    val, err := get()
    if err != nil {
        do1()
        do2()
        return nil, err
    }

    //or can use this( may be no need to add this):
    err ? {
        do1()
        do2()
        return nil, err
    }
}

[seankhliao]

Please fill out https://github.com/golang/proposal/blob/master/go2-language-changes.md when proposing language changes

[adonovan]

Also, there have been a great many proposals attempting to improve error handling. Any new one should acknowledge the challenges and lessons of those proposals to avoid merely re-litigating.

[chad-bekmezian-snap]

This does nothing to improve error handling either. It just provides short hand to ignore an error

[gopherbot]

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)