[Issue 14553] The return types of std.array.array for narrow strings conflicts with its documentation

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14553

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com
 Resolution|INVALID |FIXED

--

[Issue 14553] The return types of std.array.array for narrow strings conflicts with its documentation

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14553

Daraban Timotei  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||daraban_timo...@tutanota.co
   ||m
 Resolution|--- |INVALID

--- Comment #2 from Daraban Timotei  ---
Documentation has changed and no longer conflicts with return types.

--

[Issue 14553] The return types of std.array.array for narrow strings conflicts with its documentation

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14553

Seb  changed:

   What|Removed |Added

   Keywords||bootcamp
 CC||greensunn...@gmail.com

--

[Issue 14553] The return types of std.array.array for narrow strings conflicts with its documentation

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14553

hst...@quickfur.ath.cx changed:

   What|Removed |Added

 CC||hst...@quickfur.ath.cx

--- Comment #1 from hst...@quickfur.ath.cx ---
The question is, should we change the code to copy the qualifiers to the
returned dchar[], or should we fix the docs to match the code?

I'm not sure why it's important to keep the qualifiers if we're creating a new
array anyway. Why not keep the code as-is and ensure that it's pure, so that
the returned array can be implicitly cast to whatever qualifiers the user
wants?

--