Wow, looks like a great QoL improvement. I have a few questions though.
Propagation of optional values is an unconventional design decision. Why have you chose it over short circuiting as in C#, JS, Swift?
What’s your opinion on error wrappers and stack trace providers that are often used in go projects complicating simple error propagation? Have you consciously avoided adding similar functionality or just haven’t thought about it yet?
I haven't think much about it, a lot of things are probably going to change. I tried to get something working as fast as I possibly could, and in two weeks, lots of corners were cut to make it happen.
Thanks for the feedback, it's good to know when something does not make sense ^^
Propagation of optional values is an unconventional design decision. Why have you chose it over short circuiting as in C#, JS, Swift?
What’s your opinion on error wrappers and stack trace providers that are often used in go projects complicating simple error propagation? Have you consciously avoided adding similar functionality or just haven’t thought about it yet?