You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do understand this is opinionated, yet if I want the memory cleared when I'm done with it, I don't want to hear it's still in a log file somewhere. In my opinion, at least by default, Zeroizing should stub Debug with:
use core::fmt::{Debug,Formatter};impl<Z>DebugforZeroizing<Z>{fnfmt(&self,fmt:&mutFormatter<'_>) -> Result<(), core::fmt::Error>{
fmt.debug_struct("Zeroizing").finish()}}
The text was updated successfully, but these errors were encountered:
Yeah, that would be OK, although it might be helpful to still display the inner type name via DebugStruct (as sourced via core::any::type_name) + finish_non_exhaustive
I don't think it's an area of responsibility for zeroize. Arguably, you should use the opaque-debug crate or add a manual opaque Debug implementation for your type which gets wrapped by Zeroizing.
I do understand this is opinionated, yet if I want the memory cleared when I'm done with it, I don't want to hear it's still in a log file somewhere. In my opinion, at least by default,
Zeroizing
should stubDebug
with:The text was updated successfully, but these errors were encountered: