News for hackers. Stuff that matters.
Re:Go Developer Survey 2022 Q2 Results by masklinn on Thursday September 08, 2022 @03:00PM (#32770393)
> If Rust was able to create the ? operator based on developer experience with its try!() macro, I don't see why Go won't be able to create its own error propagation operator based on developer experience with its "if err != nil { return err }" idioms.

Because Go does not have declarative macros. So while Rust got something like 25 versions out of try! before considering that it’s worth an operator (but it could well have gone with an other pattern if one had arisen) that’s not really an option for go.

There are no comments on this comment yet.