exceptions VS either

I see. Do you think rethrowing the original exception is the the right approach in all cases, or only in this case? In the documentation I wrote for the exceptions package, I recommend to let the release block's exceptions take priority, to match base's behavior. Should I recommend the opposite?

Restricting what can go into a Result in the error variant is quite restrictive. It's often very convenient to use Result as a sort of "this or that" type without any connotations about errors, particularly as an internal convenience. Arguably one might want to use either instead, but it's a lot of ceremony to bring that in for simple use cases.

P.S. you can use either to make it work on stable rustc

The European Union does not have as large a software industry as the USA so there would be a less strong argument of government/corporate competition. It could take the form of government grants depending on the size. My rationale is that governments benefit from the general prosperity of open source more so than solo authors or small companies.

I am restricting the scope to simple and small libraries where investment is more clearly beneficial unlike Tensorflow as that is large and complex.

Here is an extreme example, the 'either' crate is a 'rayon' dependency and many others. Paradoxically a project of this size likely does not need funding but it is really important.

https://github.com/bluss/either