On Saturday, 28 February 2015 at 23:03:23 UTC, Walter Bright
wrote:
On 2/28/2015 2:31 AM, bearophile wrote:
Zach the Mystic:
You can see exactly how D works by looking at how Kenji
spends his time. For a
while he's only been fixing ICEs and other little bugs which
he knows for
certain will
On Mon, 02 Mar 2015 00:48:54 +, Zach the Mystic wrote:
I don't think anybody disagrees with this. Kenji's a miracle.
he's like Chuck Norris, only better. ;-)
signature.asc
Description: PGP signature
On Sunday, 1 March 2015 at 11:30:52 UTC, bearophile wrote:
Walter Bright:
Actually, Kenji fearlessly deals with some of the hardest bugs
in the compiler that require a deep understanding of how the
compiler works and how it is supposed to work. He rarely does
trivia. I regard Kenji's
On 2015-02-28 22:11, Andrei Alexandrescu wrote:
I've pushed for trello for a good while, it didn't catch up. -- Andrei
There's something called HuBoard [1], project management for Github
issues. I haven't used it myself but might be worth taking a look at.
Although it looks like you need
Walter Bright:
Actually, Kenji fearlessly deals with some of the hardest bugs
in the compiler that require a deep understanding of how the
compiler works and how it is supposed to work. He rarely does
trivia. I regard Kenji's contributions as invaluable to the
community.
But my point was
On Saturday, 28 February 2015 at 21:11:54 UTC, Andrei
Alexandrescu wrote:
On 2/28/15 12:20 PM, Sativa wrote:
I'm curious if project management(e.g., MS Project) is used to
optimize
and clarify goals for the D language?
I've pushed for trello for a good while, it didn't catch up. --
Andrei
Andrei Alexandrescu:
I'm following with interest the discussion My Reference Safety
System (DIP???). Right now it looks like a lot of work - a
long opener, subsequent refinements, good discussion. It also
seems just that - there's work but there's no edge to it yet;
right now a DIP along
On Friday, 27 February 2015 at 21:19:31 UTC, Andrei Alexandrescu
wrote:
On 2/27/15 1:07 PM, H. S. Teoh via Digitalmars-d wrote:
What about this, if we're serious about @safe
actually*guaranteeing*
anything: after 2.067 is released, we reimplement @safe by
making it
reject every language
Zach the Mystic:
You can see exactly how D works by looking at how Kenji spends
his time. For a while he's only been fixing ICEs and other
little bugs which he knows for certain will be accepted.
I agree that probably there are often better ways to use Kenji
time for the development of D.
On 2/28/2015 2:31 AM, bearophile wrote:
Zach the Mystic:
You can see exactly how D works by looking at how Kenji spends his time. For a
while he's only been fixing ICEs and other little bugs which he knows for
certain will be accepted.
I agree that probably there are often better ways to use
On Saturday, 28 February 2015 at 21:11:54 UTC, Andrei
Alexandrescu wrote:
On 2/28/15 12:20 PM, Sativa wrote:
I'm curious if project management(e.g., MS Project) is used to
optimize
and clarify goals for the D language?
I've pushed for trello for a good while, it didn't catch up. --
Andrei
On 2/28/15 12:20 PM, Sativa wrote:
I'm curious if project management(e.g., MS Project) is used to optimize
and clarify goals for the D language?
I've pushed for trello for a good while, it didn't catch up. -- Andrei
On 2/27/2015 2:42 AM, Dominikus Dittes Scherkl wrote:
How can we make progress,
Look at the changelog, there's tremendous progress.
On 2/28/15 7:53 AM, Marc =?UTF-8?B?U2Now7x0eiI=?= schue...@gmx.net
wrote:
On Friday, 27 February 2015 at 21:19:31 UTC, Andrei Alexandrescu wrote:
On 2/27/15 1:07 PM, H. S. Teoh via Digitalmars-d wrote:
What about this, if we're serious about @safe actually*guaranteeing*
anything: after 2.067
On Saturday, 28 February 2015 at 10:40:32 UTC, bearophile wrote:
Andrei Alexandrescu:
I'm following with interest the discussion My Reference
Safety System (DIP???). Right now it looks like a lot of work
- a long opener, subsequent refinements, good discussion. It
also seems just that -
On 2/27/2015 7:33 AM, H. S. Teoh via Digitalmars-d wrote:
@safe has some pretty nasty holes right now... like:
https://issues.dlang.org/show_bug.cgi?id=5270
https://issues.dlang.org/show_bug.cgi?id=8838
https://issues.dlang.org/show_bug.cgi?id=12822
On Friday, 27 February 2015 at 02:58:31 UTC, Andrei Alexandrescu
wrote:
On 2/26/15 6:17 PM, H. S. Teoh via Digitalmars-d wrote:
On Thu, Feb 26, 2015 at 05:57:53PM -0800, Andrei Alexandrescu
via Digitalmars-d wrote:
On 2/26/15 5:48 PM, Zach the Mystic wrote:
I sometimes feel so bad for Kenji,
On 2/27/15 1:09 AM, John Colvin wrote:
On Friday, 27 February 2015 at 02:58:31 UTC, Andrei Alexandrescu wrote:
I should add, however, that effort in and by itself does not warrant
approval per se. Labor is a prerequisite of any good accomplishment,
but is not all that's needed.
Everyone's a
Andrei Alexandrescu:
Safety is good to have, and the simple litmus test is if you
slap @safe: at the top of all modules and you use no @trusted
(or of course use it correctly), you should have memory safety,
guaranteed.
I have suggested to switch to @safe by default:
On 2/26/15 8:21 PM, Zach the Mystic wrote:
Can I ask you a general question about safety: If you became convinced
that really great safety would *require* more function attributes, what
would be the threshold for including them? I'm trying to go the whole
hog with safety, but I'm paying what
On Fri, Feb 27, 2015 at 06:02:57AM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
[...]
Safety is good to have, and the simple litmus test is if you slap
@safe: at the top of all modules and you use no @trusted (or of course
use it correctly), you should have memory safety, guaranteed.
On Friday, 27 February 2015 at 14:02:58 UTC, Andrei Alexandrescu
wrote:
Safety is good to have, and the simple litmus test is if you
slap @safe: at the top of all modules and you use no @trusted
(or of course use it correctly), you should have memory safety,
guaranteed.
A feature that is
On 2/27/15 7:33 AM, H. S. Teoh via Digitalmars-d wrote:
On Fri, Feb 27, 2015 at 06:02:57AM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
[...]
Safety is good to have, and the simple litmus test is if you slap
@safe: at the top of all modules and you use no @trusted (or of course
use it
On Friday, 27 February 2015 at 15:35:46 UTC, H. S. Teoh wrote:
@safe has some pretty nasty holes right now... like:
https://issues.dlang.org/show_bug.cgi?id=5270
https://issues.dlang.org/show_bug.cgi?id=8838
My new reference safety system:
On Fri, Feb 27, 2015 at 07:57:22AM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
On 2/27/15 7:33 AM, H. S. Teoh via Digitalmars-d wrote:
On Fri, Feb 27, 2015 at 06:02:57AM -0800, Andrei Alexandrescu via
Digitalmars-d wrote:
[...]
Safety is good to have, and the simple litmus test is
On 2/27/15 1:07 PM, H. S. Teoh via Digitalmars-d wrote:
What about this, if we're serious about @safe actually*guaranteeing*
anything: after 2.067 is released, we reimplement @safe by making it
reject every language construct by default.
I don't think this is practical. It's a huge amount of
On Friday, 27 February 2015 at 21:09:51 UTC, H. S. Teoh wrote:
No, what I meant was that in an assume safe unless proven
otherwise
system, there's bound to be holes because the combinatorial
explosion of
feature combinations makes it almost certain there's *some*
unsafe
combination we haven't
On Friday, 27 February 2015 at 02:58:31 UTC, Andrei Alexandrescu
wrote:
I should add, however, that effort in and by itself does not
warrant approval per se. Labor is a prerequisite of any good
accomplishment, but is not all that's needed.
Everyone's a Marxist when it comes to their own
On Thursday, 26 February 2015 at 20:35:04 UTC, deadalnix wrote:
Yes, I don't care about the specific enum case, in fact, that
is one of the least offender and this is why I choose it as an
example here.
Hmm. I still consider it a major issue and thought we agreed to
introduce final enum to be
On Friday, 27 February 2015 at 21:09:51 UTC, H. S. Teoh wrote:
https://issues.dlang.org/show_bug.cgi?id=12822
https://issues.dlang.org/show_bug.cgi?id=13442
https://issues.dlang.org/show_bug.cgi?id=13534
https://issues.dlang.org/show_bug.cgi?id=13536
On Fri, 27 Feb 2015 06:34:40 +, weaselcat wrote:
On Friday, 27 February 2015 at 02:46:57 UTC, ketmar wrote:
On Thu, 26 Feb 2015 18:13:12 -0800, Jonathan M Davis via Digitalmars-d
wrote:
whereas creating a PR for dmd will sometimes put things in a position
where Walter finally approves
On 2/26/2015 6:58 PM, Andrei Alexandrescu wrote:
I should add, however, that effort in and by itself does not warrant approval
per se. Labor is a prerequisite of any good accomplishment, but is not all
that's needed.
Yeah, that's always a problem. Ideally, how much work someone put into a
On Friday, 27 February 2015 at 02:46:57 UTC, ketmar wrote:
On Thu, 26 Feb 2015 18:13:12 -0800, Jonathan M Davis via
Digitalmars-d
wrote:
whereas creating a PR for dmd will sometimes put things in a
position
where Walter finally approves it (or rejects it) rather than
simply
discussing it
On Thursday, 26 February 2015 at 11:10:16 UTC, Paolo Invernizzi
wrote:
I think the real problem goes clearly beyond enums, it's an
overall approach to changes in the D language itself.
I join to deadalnix's worries.
---
Paolo
Yes, I don't care about the specific enum case, in fact, that is
On Wednesday, February 25, 2015 21:06:53 deadalnix via Digitalmars-d wrote:
Here is something I've noticed going on various time, recently in
the memory management threads, but as to avoid an already heated
debate, I'll use enum types as an example.
We have a problem with the way enums are
On Thursday, 26 February 2015 at 09:49:26 UTC, Jonathan M Davis
wrote:
On Wednesday, February 25, 2015 21:06:53 deadalnix via
Digitalmars-d wrote:
I'll use enum types as an example.
snip
I've seen this attitude going on on various topics. This is the
surest and fastest way to end up with
On Friday, 27 February 2015 at 01:33:58 UTC, Jonathan M Davis
wrote:
Well, I suspect that each case would have to be examined
individually to
decide upon the best action, but I think that what it comes
down to is the
same problem that we have with getting anything done around
here - someone
On Friday, February 27, 2015 01:48:00 Zach the Mystic via Digitalmars-d wrote:
On Friday, 27 February 2015 at 01:33:58 UTC, Jonathan M Davis
wrote:
Well, I suspect that each case would have to be examined
individually to
decide upon the best action, but I think that what it comes
down to
On Friday, 27 February 2015 at 02:58:31 UTC, Andrei Alexandrescu
wrote:
I'm following with interest the discussion My Reference Safety
System (DIP???). Right now it looks like a lot of work - a
long opener, subsequent refinements, good discussion. It also
seems just that - there's work but
On Thursday, February 26, 2015 20:35:02 deadalnix via Digitalmars-d wrote:
On Thursday, 26 February 2015 at 11:10:16 UTC, Paolo Invernizzi
wrote:
I think the real problem goes clearly beyond enums, it's an
overall approach to changes in the D language itself.
I join to deadalnix's
On Thu, Feb 26, 2015 at 05:57:53PM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
On 2/26/15 5:48 PM, Zach the Mystic wrote:
I sometimes feel so bad for Kenji, who has come up with several
reasonable solutions for longstanding problems, *and* implemented
them, only to have them be frozen
On Thu, 26 Feb 2015 18:13:12 -0800, Jonathan M Davis via Digitalmars-d
wrote:
whereas creating a PR for dmd will sometimes put things in a position
where Walter finally approves it (or rejects it) rather than simply
discussing it and getting nowhere.
oh, i see. i really enjoy multiple `alias
On 2/26/15 6:17 PM, H. S. Teoh via Digitalmars-d wrote:
On Thu, Feb 26, 2015 at 05:57:53PM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
On 2/26/15 5:48 PM, Zach the Mystic wrote:
I sometimes feel so bad for Kenji, who has come up with several
reasonable solutions for longstanding
On 2/26/15 5:48 PM, Zach the Mystic wrote:
I sometimes feel so bad for Kenji, who has come up with several
reasonable solutions for longstanding problems, *and* implemented them,
only to have them be frozen for *years* by indecision at the top.
Yah, we need to be quicker with making decisions,
Here is something I've noticed going on various time, recently in
the memory management threads, but as to avoid an already heated
debate, I'll use enum types as an example.
We have a problem with the way enums are defined. If you have :
enum E { A, B, C }
E e;
We have (1)
final switch(e)
On 2015-02-25 22:06, deadalnix wrote:
Here is something I've noticed going on various time, recently in the
memory management threads, but as to avoid an already heated debate,
I'll use enum types as an example.
We have a problem with the way enums are defined. If you have :
enum E { A, B, C }
On Wednesday, 25 February 2015 at 21:06:54 UTC, deadalnix wrote:
This very conversation went on in a very lengthy thread a while
ago (note, for SDC, I just dropped (2), typeof(E.A | E.B) ==
int and I consider it a closed issue).
If you keep the type, you can decompose the flag set when
47 matches
Mail list logo
