da911aec7a
Currently, `PrivateAggregationBudgeter` defers storage initialization by binding a callback to a private method in the constructor and lazily running the callback the first time storage is needed. Subjectively, it's a little confusing for the reader because they have to untangle this indirect control flow. This CL removes the callback and instead calls the private method directly. The tradeoff is that we now have to explicitly store the method's parameters as private fields. Another benefit of this more explicit control flow is that it eliminates the `WeakPtr` bound to the callback. I found that `WeakPtr` a little confusing because it implied that there's a chance that we'd initialize storage after destroying `this`. Change-Id: I8925196fe3b7762d5e4ebd8918c44f449b357eb2 Bug: 398173022 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6287446 Commit-Queue: Dan McArdle <dmcardle@chromium.org> Reviewed-by: Alex Turner <alexmt@chromium.org> Cr-Commit-Position: refs/heads/main@{#1423293}
Private Aggregation API
This directory implements the Private Aggregation API.
TODO(alexmt): Expand this README.