Re: [PATCH v8 3/4] rust: fmt: Default raw pointer formatting to HashedPtr

[Andy Shevchenko <andriy.shevchenko@linux.intel.com>]

On Tue, Jan 06, 2026 at 05:18:41PM +0000, Alice Ryhl wrote:
> On Tue, Jan 06, 2026 at 05:45:37PM +0100, Petr Mladek wrote:
> > On Mon 2026-01-05 08:19:49, Alice Ryhl wrote:

...

> If I write this code in normal Rust:
> 
> 	let ptr = &3 as *const i32;
> 	println!("{:?}", ptr);
> 	println!("{:017?}", ptr);
> 	println!("{:17?}", ptr);
> 
> it prints:
> 
> 0x602ae0ec95d8
> 0x000602ae0ec95d8
>    0x602ae0ec95d8
> 
> If we implement {:?} on a raw pointer type (and {:p} on reference type)
> to use scnprintf with a stack buffer for the string representation, then
> we lose this flexibility. (Or we need additional effort to pass through
> the various ways you can configure it to scnprintf.)

I think the field width or variations make a little sense on pointers. AFAIR
printf() in kernel ignores field width and padding modifications to a pointer.
Only size of the end buffer may cut the string in the middle.


-- 
With Best Regards,
Andy Shevchenko