eris VS Shift

What really sucks IMO is that there's no compiler support for exhaustive error checks, the amount of boilerplate for handling errors, no sum types like Rust, horrible stacktraces unless you use something like eris, the ease with which you can ignore errors, all make for really poor error handling as it remains. It is now the #1 challenge that devs report for Go as per their own survey. We might see some improvements on this front at some point and seeing the new errors.Join stuff is giving me hope

Attaching stacktraces to errors is one way to make errors more readable. Go has notoriously unreadable errors and when you log the error, the logging function is now at the top of the stack rather than where the error actually originated. There needs to be a simple function that adds some default wrapping when you return an error because as it is, you need packages like Eris to make the errors even halfway readable

Actually just stumbled over eris which seems decent.

It also might be worth checking out Shift this seems to be some sort of EventKit wrapper for SwiftUI from UIKit. Another really useful way is Github, honestly looking at how other people are also tackling the problem can be such a good way to improve your code quality and also find quicker solutions. For example: MeetingSwiftUI (credit: shrtlist) - this could be a good base, look at how this user has gone about EventKit, 9/10 it won't answer directly what you are looking for but it sometimes can be the inspiration (and give you the know how) to get you across that line and develop it yourself. Be nice though, if you find it useful give it a star ;)

I based my own usage on this lib to suit my needs https://github.com/vinhnx/Shift