On Thursday, 28 May 2020 at 16:01:35 UTC, Johannes Pfau wrote:
Am Thu, 28 May 2020 12:28:16 + schrieb Sebastiaan Koppe:
If it does come back to haunt him, he can always add a DIP to
make extern(!D) @system by default. It won't invalidate any
work.
This would be another round of massively
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as
On Friday, 29 May 2020 at 11:04:00 UTC, jmh530 wrote:
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
[...]
Thank you Walter. I am sure this was not an easy decision, and
I respect how you have handled the response.
[...]
I would think that Phobis maintainers would make good
On 5/28/20 9:53 PM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:` as the
first line in all your project modules, and annotate individual
functions otherwise as necessary. For modules with C declarations, do as
you think best.
On 5/29/20 12:53 AM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:` as the
first line in all your project modules, and annotate individual
functions otherwise as necessary. For modules with C declarations, do as
you think best.
On Friday, 29 May 2020 at 05:08:44 UTC, Bruce Carneal wrote:
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions
On 2020-05-27 06:59:28 +, Bruce Carneal said:
Walter has confirmed that this is indeed the case. As you can read a
few posts up his response to my "What am I missing?" query was "Nothing
at all."
Yes, it's really that bad.
Will it be possible to see a report of these "greenwashed"
On Saturday, 9 May 2020 at 11:33:08 UTC, notna wrote:
On Friday, 8 May 2020 at 00:46:04 UTC, Basile B. wrote:
Sorry, I'm tempted to drop official Windows support good. I
have an old win7 DVD but I'd prefer if someone who actually
uses Windows could fix this. For now let's talk here
Thank you Walter.
On Friday, 29 May 2020 at 06:55:07 UTC, Robert M. Münch wrote:
On 2020-05-27 06:59:28 +, Bruce Carneal said:
Walter has confirmed that this is indeed the case. As you can
read a few posts up his response to my "What am I missing?"
query was "Nothing at all."
Yes, it's really that bad.
On 29.05.20 06:53, Walter Bright wrote:
The subject says it all.
Thanks! For the record, this would have been my preference:
fix @safe, @safe by default >
fix @safe, @system by default >
don't fix @safe, @system by default >
don't fix @safe, @safe by default
While this retraction
On Friday, 29 May 2020 at 11:33:01 UTC, Sebastiaan Koppe wrote:
On Thursday, 28 May 2020 at 16:01:35 UTC, Johannes Pfau wrote:
[snip]
This would be another round of massively breaking user code.
The breakage will be split in two rounds, but the amount of
code needed to be modified would be
On Friday, 29 May 2020 at 12:22:07 UTC, Steven Schveighoffer
wrote:
On 5/29/20 12:53 AM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as
On Friday, 29 May 2020 at 13:11:29 UTC, Andrei Alexandrescu wrote:
...
Unrelated to this decision, I wanted to apologize for having
lowered the quality of discourse in this forum.
I think you should. To be honest first I thought it was a fake
account, because your behavior wasn't great
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as
On 5/29/20 12:53 AM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:` as the
first line in all your project modules, and annotate individual
functions otherwise as necessary. For modules with C declarations, do as
you think best.
On 28.05.20 17:35, Atila Neves wrote:
https://code.dlang.org/packages/unit-threaded
You got a bad @trusted:
import unit_threaded.light: check;
void main() @safe
{
check!((int a) @system {
/* ... can do unsafe stuff here ... */
return true;
});
}
I searched
On Friday, 29 May 2020 at 13:11:29 UTC, Andrei Alexandrescu wrote:
On 5/29/20 12:53 AM, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as
Hi,
This tutorial describes how to run a vibe-d http server within a
docker scratch image for the purpose of security.
https://d-land.sepany.de/tutorials/cloud/sichere-docker-images-fuer-cloud-anwendungen-erstellen/
Kind regards
Andre
On 2020-05-29 16:22, Paul Backus wrote:
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:` as the
first line in all your project modules, and annotate individual
functions otherwise as
On 2020-05-29 16:13, SashaGreat wrote:
On Friday, 29 May 2020 at 13:11:29 UTC, Andrei Alexandrescu wrote:
...
Unrelated to this decision, I wanted to apologize for having lowered
the quality of discourse in this forum.
I think you should. To be honest first I thought it was a fake account,
On Friday, 29 May 2020 at 08:04:12 UTC, Basile B. wrote:
I've fixed it yesterday
(https://gitlab.com/basile.b/dexed/-/commit/730c2a4e6e1ae18d603d91c471bf3b6459ce7b52) using my mom's laptop ^^.
Fortunately I've found an old post from p0nce
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
Thanks a lot for your effort!
Judging by the responses, there should be another attempt after
addressing some issues.
I have an idea that could mitigate greenwashing of extern (I know
everyone hates that
On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as
On Friday, 29 May 2020 at 21:18:13 UTC, Walter Bright wrote:
On 5/29/2020 2:07 AM, Timon Gehr wrote:
It would be great if `@safe:` did not affect declarations that
would otherwise infer annotations.
The idea is the simple, general rule that:
attribute declaration;
attribute {
On Thursday, May 28, 2020 10:53:07 PM MDT Walter Bright via Digitalmars-d-
announce wrote:
> The subject says it all.
>
> If you care about memory safety, I recommending adding `safe:` as the first
> line in all your project modules, and annotate individual functions
> otherwise as necessary. For
On Friday, 29 May 2020 at 20:36:12 UTC, Walter Bright wrote:
On 5/29/2020 7:22 AM, Paul Backus wrote:
This is sad news. I was excited for @safe-by-default, and had
hoped that the issue with extern(C) could be solved without
throwing DIP 1028 away entirely.
I watched a documentary on Clive
On Friday, 29 May 2020 at 20:36:12 UTC, Walter Bright wrote:
Kenny G (famous clarinet player)
Soprano saxophone, not clarinet. They look similar, and are both
Bb instruments (I know there are non Bb clarinets), but they
don't sound that similar to me. Kenny G is also sometimes heard
on
On Friday, 29 May 2020 at 21:18:13 UTC, Walter Bright wrote:
The idea is the simple, general rule that:
There's already exceptions to that.
public public void foo() {}
is an error, whereas
public:
public void foo() {}
is not.
Having a simple, general rule with maybe a less favorable
On Friday, May 29, 2020 6:48:20 AM MDT Meta via Digitalmars-d-announce wrote:
> On Friday, 29 May 2020 at 12:22:07 UTC, Steven Schveighoffer
>
> wrote:
> > On 5/29/20 12:53 AM, Walter Bright wrote:
> >> The subject says it all.
> >>
> >> If you care about memory safety, I recommending adding
On 5/29/2020 2:07 AM, Timon Gehr wrote:
It would be great if `@safe:` did not affect declarations that would otherwise
infer annotations.
The idea is the simple, general rule that:
attribute declaration;
attribute { declaration; }
attribute: declaration;
behave the same way.
C++ is
On 5/29/2020 7:22 AM, Paul Backus wrote:
This is sad news. I was excited for @safe-by-default, and had hoped that the
issue with extern(C) could be solved without throwing DIP 1028 away entirely.
I watched a documentary on Clive Davis (famous recording executive) the other
day. He would
On 5/29/2020 4:47 PM, Bastiaan Veelo wrote:
I’m not sure who in this analogy is the Kenny G and who the Clive Davis,
Haha, I was deliberately vague about that, so people could interpret it as they
pleased.
Off topic, and without extending the analogy, I had never heard about Kenny G
He
On 5/29/2020 3:36 AM, Ali Çehreli wrote:
Thank you! Which meme did it? :o)
My secret!
35 matches
Mail list logo
