amosonn

I can probably write this myself, but it might take me a while to get acquainted enough with the code. Could you please give me pointers where to look? Conversely,...

Thanks! Yes, I figured up as much, already implemented this as an option. I will send a pull request when I get good internet access. The only thing that I...

Coming next, I'm planning to write a lib which parses this xml and makes it available via fusermount. I don't think it fits here, but I will update anyway, for...

Yes, that what it means. It's of course contrived, but it is just a minimal reproduction from a larger schema I had. I think that also other subschemas inside `additionalProperties`...

There's a similar (but slightly different-looking) version of this in the RFC itself; maybe it's better to use that to be safe: https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md#stack-pinning-api-potential-future-extension On Sat, Jun 1, 2019, 12:26 real...

It seems there might be some issue with the drop guarantees: https://doc.rust-lang.org/std/pin/index.html#drop-guarantee which make the RFC version unsound. The problem is, that if you just pin something and then "go...

What size is the database, what do you store there? Is there some sample, or where is the relevant code?

The first thing that comes to mind is that a key-value store, something like mongo-db, can already be an improvement over re-writing a json-file. I think the complexity there is...

I was going suggest a different approach: a blanket-impl for things implementing the two traits used in the implementation: `Default` and `DerefMut` into `[u8]`. This doesn't work though, because `PrivateKey`...

No, I meant it the other way around, that maybe `PrivateKey` *shouldn't* implement `DerefMut`, only `Deref`. The boilerplate impls could be replaced with a blanket impl for things which do...