On Thursday, 22 March 2018 at 19:14:06 UTC, Seb wrote:
Making all high-level functions of Phobos @safe
-----------------------------------------------
There's are still some functions in Phobos which could be
@safe, but aren't.
I was going to ask this in Slack but since this thread is already
here, why not.
What are we going to do about C library calls in std.zlib and
std.zip? I'm really uncomfortable about adding @trusted to the
zlib calls, as it's different than calling C functions from the
std library. There's no issue in reality with marking a
malloc/free pair as trusted when it's verified to not escape. But
there's really no garuntee about the safety of third party
libraries. What if there's a Heartbleed level bug in zlib and we
marked it as @trusted?
Should we just resign ourselves to the fact that some functions
are going to be @system no matter what?
