Philipp Schuster

Theoretically you can already call `unwrap_or` on it, but yes, you need one additional `unwrap` or `expect` - I see. I don't think that this is a problem, TBH. 1....

For the record: I've got a working PoC: #7150

Thanks for working on this!

I don't think you can drop the Cargo.lock and this:  In theory, yes, you can provide the Cargo.lock externally.. but this is a pain to keep in sync. I'm...

I rebased the PR. Are we good to go @NULLx76 ?

Why was this closed? Are you in favor of this change or not? :) I can restart the work if you want

I think this can be closed, because of #7085 et. al.?

So far, the applied approach is unspoken and was never really discussed. "We just did it somehow", mostly. From my point of view, it was a 66.6% prefer non-alloc and...

I think we can close this. Reopen if necessary. TL;DR: Make it alloc-free where **easily** doable. Otherwise, utilize `alloc` to build nice abstractions

Missing types and functions, or generally speaking functionality, are not a major blocker for a 1.0 release IMHO, as the major component in x.y.z is for the API itself and...