On Friday, 16 May 2025 at 09:42:20 UTC, Kagamin wrote:
On Wednesday, 14 May 2025 at 11:38:59 UTC, Nick Treleaven wrote:
So `to!string` is bad for generic code. Want to represent the
address of a byte* as hex in a string, fine. Oh now the
pointer's element type is char - wait, why isn't the resu
On Wednesday, 14 May 2025 at 11:38:59 UTC, Nick Treleaven wrote:
So `to!string` is bad for generic code. Want to represent the
address of a byte* as hex in a string, fine. Oh now the
pointer's element type is char - wait, why isn't the result hex
any more?
try `to!(string,void*)`?
On Wednesday, 14 May 2025 at 11:38:59 UTC, Nick Treleaven wrote:
On Wednesday, 14 May 2025 at 03:36:40 UTC, Jonathan M Davis
wrote:
to!string definitely deals with null-terminated strings, or it
wouldn't work at all. It's not the kind of thing that would
work by accident.
I don't think it's g
On Wednesday, May 14, 2025 5:38:59 AM Mountain Daylight Time Nick Treleaven via
Digitalmars-d-learn wrote:
> On Wednesday, 14 May 2025 at 03:36:40 UTC, Jonathan M Davis wrote:
> > to!string definitely deals with null-terminated strings, or it
> > wouldn't work at all. It's not the kind of thing th
On Wednesday, 14 May 2025 at 03:36:40 UTC, Jonathan M Davis wrote:
to!string definitely deals with null-terminated strings, or it
wouldn't work at all. It's not the kind of thing that would
work by accident.
I don't think it's good API design:
Pointer to string conversions convert the pointer
