On Saturday, 30 May 2020 at 20:29:37 UTC, Adam D. Ruppe wrote:
We should make this actually work for everything.
1) Make inferred_attr: NOT apply to template/auto functions.
2) Add inverse attributes for all things. (or tri-state,
true/false/null)
3) Solve the child scope problem somehow consi
On Sunday, 31 May 2020 at 19:15:19 UTC, Walter Bright wrote:
On 5/30/2020 4:39 AM, Nick Treleaven wrote:
To preserve this, then please can we have `@safe module foo;`.
This would change the default on a module basis to @safe, but
still infer e.g. function template bodies as @system where
neces
On 5/30/2020 4:39 AM, Nick Treleaven wrote:
To preserve this, then please can we have `@safe module foo;`. This would change
the default on a module basis to @safe, but still infer e.g. function template
bodies as @system where necessary. This feature would allow modules from
different projects
On Saturday, 30 May 2020 at 20:29:37 UTC, Adam D. Ruppe wrote:
On Saturday, 30 May 2020 at 20:14:04 UTC, Steven Schveighoffer
wrote:
On 5/30/20 4:02 PM, Andrei Alexandrescu wrote:
module foo; @safe:
Again, not the same. Read the full thread that you quoted
above.
And even aside from infere
On Saturday, 30 May 2020 at 20:14:04 UTC, Steven Schveighoffer
wrote:
On 5/30/20 4:02 PM, Andrei Alexandrescu wrote:
module foo; @safe:
Again, not the same. Read the full thread that you quoted above.
And even aside from inference, it doesn't actually work for most
the attributes.
@safe i
On Friday, 29 May 2020 at 05:08:44 UTC, Bruce Carneal wrote:
Thanks Walter.
Thanks to everyone in the commmunity for being nice and saying
"Thank you." As a cautionary tale, Guido Van Rossum, former BDFL
of Python, resigned over flamewars on the := operator in Python,
the same arguments were
On 5/30/20 4:02 PM, Andrei Alexandrescu wrote:
On 5/30/20 7:39 AM, Nick Treleaven wrote:
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
On 5/30/20 7:39 AM, Nick Treleaven wrote:
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:
attrib
On Saturday, 30 May 2020 at 16:17:49 UTC, Steven Schveighoffer
wrote:
+1 this would be perfect.
Not sure if this would work either, but both of these are
already reserved words:
default @safe:
-Steve
It would probably have to be something more like
`default(@safe)`, since `default @safe:
On 5/30/20 7:39 AM, Nick Treleaven wrote:
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:
attrib
On Friday, 29 May 2020 at 21:38:40 UTC, Adam D. Ruppe wrote:
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.
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 { declaration;
On 5/29/2020 2:38 PM, Adam D. Ruppe wrote:
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.
Is it really an
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/2020 2:53 AM, solidstate1991 wrote:
Can we get a compiler flag that will enable safe by default for people who might
want it?
It would balkanize the language.
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 think one important takeaway from this should be that people
On 5/29/2020 3:36 AM, Ali Çehreli wrote:
Thank you! Which meme did it? :o)
My secret!
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 other
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 w
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 Dav
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 m
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 `safe:
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 { declaration;
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
eff
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 ful
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 advise
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.
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 ter
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 necessary.
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,
b
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 ne
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 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 (Techn
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.
F
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 n
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.
F
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 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/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.
Fo
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
Thank you Walter.
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 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 ot
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
Am 29.05.20 um 06:53 schrieb Walter Bright:
> 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
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
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.
For everyone else, carry on as before.
48 matches
Mail list logo
