Tim Diekmann

> * `Hooks` (could be easily confused with the `Hook` trait) > * `Hooks::push` -> `Hooks::add`? Do we need `Hooks` to be public or could we do this by having...

> We could replace the old `set_debug_hook` with the new `Hooks`, we then wouldn't need `add_debug_hook`. Users who would want complete customization could use a newtype instead. What do you...

> Even if we have the serde implementation, I think it would still be beneficial to have the ability to override the `Debug` implementation so that it's easier to use...

> Would an extended `Display` use multiple lines? I think this would be fine. As `Display` is usually user-facing, only user information should be displayed here (e.g. omitting the code...

> thinking Maybe the alternate display formatting should be the non-alternate `Debug` display? I think that `Debug` is general enough for the user (and looks good enough) I don't see...

> small update: I think I have finalized most things. Documentation should mostly be in place. I now only need to write the necessary tests and snapshot tests. Once those...

Yes, that is way too long 😄 We probably want to combine a few feature flags in order to cut the feature-powerset down.

> While this is not merged in I use my repo to run actions Works like a charm, thank you!

Thanks for the feedback @Wodann! I'll look into your commit as soon as I have a bit more free time :smile: > For the bump allocator use case, the BuildAllocRef...

@Wodann with your use case, I guess you mean your bump allocator and https://github.com/TimDiekmann/alloc-wg/pull/11? Yes, I have tested around with it. I think, the problem isn't the mutable `AllocRef`, but...