Thread overview
[Issue 16535] writeln("a") is safe, stdout.writeln("a") is not
Sep 24, 2016
Walter Bright
Sep 25, 2016
Jack Stouffer
Sep 25, 2016
Jack Stouffer
September 24, 2016
https://issues.dlang.org/show_bug.cgi?id=16535

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |safe
                 CC|                            |bugzilla@digitalmars.com

--
September 25, 2016
https://issues.dlang.org/show_bug.cgi?id=16535

Jack Stouffer <jack@jackstouffer.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@jackstouffer.com

--- Comment #1 from Jack Stouffer <jack@jackstouffer.com> ---
Currently, stdout.writeln("a") should be unsafe.

This is another example of the root cause of both https://issues.dlang.org/show_bug.cgi?id=15768 and https://issues.dlang.org/show_bug.cgi?id=13727

The root cause being that large parts of std.stdio are not, in reality, memory safe and are still marked as @trusted.

--
September 25, 2016
https://issues.dlang.org/show_bug.cgi?id=16535

Jack Stouffer <jack@jackstouffer.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=15768

--
July 17
https://issues.dlang.org/show_bug.cgi?id=16535

Jack Stouffer <jack@jackstouffer.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |17658

--