[Issue 18632] enable use of fromStringz with char[n]

2021-07-16 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=18632

Dlang Bot  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Dlang Bot  ---
dlang/phobos pull request #8164 "Fix issue 18632 - enable use of fromStringz
with char[n]" was merged into master:

- 66698dc5f5daed7121cf3715f4be565208478d19 by dkorpel:
  Fix issue 18632 - enable use of fromStringz with char[n]

https://github.com/dlang/phobos/pull/8164

--

[Issue 18632] enable use of fromStringz with char[n]

2021-07-11 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=18632

Dlang Bot  changed:

   What|Removed |Added

   Keywords||pull

--- Comment #2 from Dlang Bot  ---
@dkorpel created dlang/phobos pull request #8164 "Fix issue 18632 - enable use
of fromStringz with char[n]" fixing this issue:

- Fix issue 18632 - enable use of fromStringz with char[n]

https://github.com/dlang/phobos/pull/8164

--

[Issue 18632] enable use of fromStringz with char[n]

2018-03-19 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=18632

Jonathan M Davis  changed:

   What|Removed |Added

 CC||issues.dl...@jmdavisprog.co
   ||m

--- Comment #1 from Jonathan M Davis  ---
(In reply to elpenguino+D from comment #0)
> This would possibly also have the benefit of being @safe and pure.

Without -dip1000, treating the result as @safe would be a huge mistake, because
slicing a static array like this is inherently unsafe. The fact that the
compiler does not treat slicing static arrays as @system without -dip1000 and
scope is a bug (and it's in bugzilla somewhere, but I don't feel like searching
for it at the moment). And on that note, the function would have to accept the
static array by ref, or it would have a huge @safety bug.

--