I'm curious what the distribution looks like between whether
people agree that extern(C) should be @safe, or @system. People
that think it should be @trusted, vote @safe, it's pretty much
the same thing.
https://www.strawpoll.me/20184671
On Wednesday, 27 May 2020 at 10:03:21 UTC, Walter Bright wrote:
It's not an acceptable solution for people who require
correctness. ZombineDev can't tell an auditor that he relies
on D-Scanner to find the problematic spots. I believe it's
unavoidable to provide an option to change the default.
On Tuesday, 26 May 2020 at 20:32:13 UTC, Paul Backus wrote:
On Tuesday, 26 May 2020 at 17:50:58 UTC, Gregory wrote:
Which will just lead people to pure @trusted: at the top of
their code to get it to compile again, with or without
extern(C) being @safe by default. Then someone that uses it as
On Tuesday, 26 May 2020 at 16:20:23 UTC, Atila Neves wrote:
On Tuesday, 26 May 2020 at 16:10:24 UTC, Bruce Carneal wrote:
On Tuesday, 26 May 2020 at 15:54:31 UTC, Bastiaan Veelo wrote:
On Tuesday, 26 May 2020 at 15:39:11 UTC, Bruce Carneal wrote:
On Tuesday, 26 May 2020 at 15:01:06 UTC,
On Tuesday, 26 May 2020 at 03:37:29 UTC, Walter Bright wrote:
On 5/25/2020 7:04 PM, Johannes Loher wrote:
Now let's compare the two different options:
1. With DIP1028 in its current form, the code will compile and
a memory corruption will actually happen. The problem might be
extremely
On Friday, 22 May 2020 at 01:22:19 UTC, Walter Bright wrote:
Consider the common (because that's how D started out) case of:
- clibrary.d
T massage_data(... many parameters ...);
... 200 more such declarations ...
- app.d --
import clibrary;
void