mirrors/arti.git/crates/tor-memquota/src/mtracker/total_qty_notifier.rs, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2024-09-04T12:26:47Ztor-memquota: Break out reclamation wakeup2024-09-04T12:26:47ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-28T15:43:43Zurn:sha1:e099d2414209f5df2431cc3d161ec7e81ae6cc23tor-memquota: Make reclamation wakeup no longer throw internal errors2024-09-04T12:26:47ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-28T15:37:36Zurn:sha1:0c823ec5061916c76516488811043917fc06d8f5
I realised a way this could happen without there being a bug.
tor-memquota: Rework optionality configuration2024-09-04T10:47:56ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-27T13:19:49Zurn:sha1:12f233e9c0f301a247edb44df67f1c60027d765e
Allow a `Config` to represent "this is supposed to be disabled".
This involves wrapping the actual built configuration in an IfEnabled.
We treat max = usize::MAX, or max being unspecified, as "disable".
We can now reporting an error during config building if max is set but
we're compiling the feature out. Conversely, we can now make
`MemoryQuotaTracker::new()` unconditional, since enabled
confiogurations are uninhabited when the feature is compiled out.
We change how we derive the setters, deriving them from the Builder.
I chose to abolish the use of derive_builder. See the new comment on
ConfigBuilder.
Rename tor-memtrack to tor-memquota2024-04-29T16:43:01ZIan Jacksonijackson@chiark.greenend.org.uk2024-04-29T12:59:15Zurn:sha1:b71a9cc99ac44ab74accf7c259ffa3de2e331ed6