> - go style err!=nill style exception handling
Is this not widely considered to be the ugliest part of the language? Why do you prefer having to do this manually?
It is, which is why the or_return[1] keyword was created.
[1]: https://odin-lang.org/docs/overview/#or_return-operator
Errors as values instead of some special language construct is generally a nice thing (IMO)
Yes it is and it's frankly odd we are still designing languages this way. It's a mess and a Result with typed errors is much more ergonomic and should be the standard. See either in scala for more.
As someone who is primarily a Go dev, I never understood this criticism and have never seen a language do it any better (but I'm open to suggestions). I think try/catch is worse. I kinda like JS's promise syntax with the `.then()` and `.catch()`, but it doesn't appear that different to Go's approach.