str4d
str4d
While looking up the history of the `heapsize` crate, I found another more recent crate implementing memory usage introspection: https://github.com/wasmerio/loupe
This crate currently implements a trait-based measurement approach, where trait impls return the amount of memory that their types requested be allocated. [`malloc_size_of`](https://github.com/servo/servo/tree/master/components/malloc_size_of) is an internal component of Servo (that...
I searched for existing crates prior to writing this one, and somehow completely missed the `heapsize` crate from the Servo devs. It takes a very similar approach to this crate,...
Closes #1.
Similarly to how `zeroize::Zeroize` can be derived, we could enable `DynamicUsage` to be derived on structs composed of subtypes that themselves implement `DynamicUsage`.
When extracting the Sapling types back into `sapling-crypto`, we added more type safety. In particular, we made the proof verifying keys typesafe by placing the `bellman` types inside opaque newtype...
https://github.com/zcash/sapling-crypto/blob/ab3aea55c0813c760e74d248bd3f16825b577514/src/builder.rs#L65-L71 In the old builder code in `zcash_primitives`, we would never pad spends. The new logic extends this with a `bundle_required` case, where the caller can force a 1-spend 2-output...
The `keys` module types are derived from some of the earliest `sapling-crypto` code. They have public internals, expose boundaries that don't make sense in end-developer applications, and are generally tricky...
Currently, we have a single `SaplingVerificationContext` which we initialize, use to verify each Spend and Output description, and then call `final_check` to verify `bindingSig`. The reason for this workflow was...