feat: a more convenient Result interface

[volmedo]

Make Results easier to use by allowing access to Ok and Err values.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
core/result/result.go	0.00%	4 Missing ⚠️

Files with missing lines	Coverage Δ
core/result/result.go	74.75% <0.00%> (-1.49%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[alanshaw]

You're goign to have to check both of these values anyways, is unwrap not sufficient?

[volmedo]

I have seen myself just checking one of them, depending on the use case, and having something you can just inline in an if feels more convenient.

[alanshaw]

It's just more API surface area to maintain and IMO Unwrap suffices. Even if you're only using 1 value - just assign to underscore, that way you're at least acknowledging you're choosing to ignore the other value it could be.

data, _ := result.Unwrap(myresult)
_, err := result.Unwrap(myresult)

[volmedo]

ok, I just wanted to streamline ifs without having to unwrap explicitly. Also, Unwrap returns the plain types (rather than pointer), which prevents you from doing a comparison with nil unless you use pointers yourself in all the type parameters when declaring receipts and results.

If the API surface is the issue, I can remove Unwrap 😝