Migrating from my fork back to Master - bits I added... about result HOT 1 CLOSED

Stupid me just thought I'd subclass Result<T> and obviously that's not going to work unless I override all the static methods.

Unfortunately, my project has ground to a halt over this as these result objects are everywhere.

My sense is that attempting to fit a single result solution into very specific applications for API result and Repository result is asking for exactly the conundrum I'm in now.

I've thought of wrapping the object containing the additional information inside a specific class, like RepoResult<T> and then using Result<RepoResult>, but at that point, it's just getting silly it seems.

I don't know how I'd extend the class and still be able to use the static helper methods, etc.

from result.