Compared to the talk at Google, I changed one of the "cool things" from threading to operator overloading. Didn't manage to talk about that - there were a million questions - although I think it's a great topic.

http://erdani.com/tdpl/2010-12-08-ACCU.pdf


Andrei

Andrei Alexandrescu wrote:
> Compared to the talk at Google, I changed one of the "cool things" from threading to operator overloading. Didn't manage to talk about that - there were a million questions - although I think it's a great topic.
> 
> http://erdani.com/tdpl/2010-12-08-ACCU.pdf


Anyone care to do the honors and post this to reddit programming?

Walter Bright <newshound2@digitalmars.com> wrote:

> Andrei Alexandrescu wrote:
>> Compared to the talk at Google, I changed one of the "cool things" from threading to operator overloading. Didn't manage to talk about that - there were a million questions - although I think it's a great topic.
>>  http://erdani.com/tdpl/2010-12-08-ACCU.pdf
>
>
> Anyone care to do the honors and post this to reddit programming?

Done.

http://www.reddit.com/r/programming/comments/eklq0/andrei_alexandrescus_talk_at_accu_silicon_valley/

-- 
Simen

Looks like someone did: http://www.reddit.com/r/programming/comments/eklq0/andrei_alexandrescus_talk_at_accu_silicon_valley/

On 12/12/10, Walter Bright <newshound2@digitalmars.com> wrote:
> Andrei Alexandrescu wrote:
>> Compared to the talk at Google, I changed one of the "cool things" from threading to operator overloading. Didn't manage to talk about that - there were a million questions - although I think it's a great topic.
>>
>> http://erdani.com/tdpl/2010-12-08-ACCU.pdf
>
>
> Anyone care to do the honors and post this to reddit programming?
>

Simen kjaeraas Wrote:

> Walter Bright <newshound2@digitalmars.com> wrote:
> 
> > Andrei Alexandrescu wrote:
> >> Compared to the talk at Google, I changed one of the "cool things" from
> >> threading to operator overloading. Didn't manage to talk about that -
> >> there were a million questions - although I think it's a great topic.
> >>  http://erdani.com/tdpl/2010-12-08-ACCU.pdf
> >
> >
> > Anyone care to do the honors and post this to reddit programming?
> 
> Done.
> 
> http://www.reddit.com/r/programming/comments/eklq0/andrei_alexandrescus_talk_at_accu_silicon_valley/

Guys, I made several sockpuppet reddit accounts to mod down the two guys criticising this thread. I recommend everyone to help us improve D's publicity by ignoring these trolls and voting them down. It has worked before, too -- reddit seems to fold the subthreads that get too many negative votes. This makes it look much better than it is.

 - G.W.

On 12/12/10 8:56 PM, Gary Whatmore wrote:
> Simen kjaeraas Wrote:
>
>> Walter Bright<newshound2@digitalmars.com>  wrote:
>>
>>> Andrei Alexandrescu wrote:
>>>> Compared to the talk at Google, I changed one of the "cool things" from
>>>> threading to operator overloading. Didn't manage to talk about that -
>>>> there were a million questions - although I think it's a great topic.
>>>>   http://erdani.com/tdpl/2010-12-08-ACCU.pdf
>>>
>>>
>>> Anyone care to do the honors and post this to reddit programming?
>>
>> Done.
>>
>> http://www.reddit.com/r/programming/comments/eklq0/andrei_alexandrescus_talk_at_accu_silicon_valley/
>
> Guys, I made several sockpuppet reddit accounts to mod down the two
> guys criticising this thread. I recommend everyone to help us improve
> D's publicity by ignoring these trolls and voting them down. It has
> worked before, too -- reddit seems to fold the subthreads that get
> too many negative votes. This makes it look much better than it is.

I think at best we focus on providing good information. One problem with nay-saying is that, when half-competent, provides misinformation.

Andrei

Hi,

Thanks for sharing the doc.

> I changed one of the "cool things" from threading to operator overloading.


May I know the reason behind the change? Is it that you intend to pick different "3 cool things" at different talks? or do you think operator overloading is 'cooler'  than concurrency?

Thanks,
Hemanth

On 12/12/10 9:50 PM, Hemanth Kapila wrote:
> Hi,
>
> Thanks for sharing the doc.
>
>     I changed one of the "cool things" from threading to operator
>     overloading.
>
> May I know the reason behind the change? Is it that you intend to pick
> different "3 cool things" at different talks? or do you think operator
> overloading is 'cooler'  than concurrency?
>
> Thanks,
> Hemanth

I thought since the video of my Google talk is already online, I better offer something new. I would have changed two of the three topics, but didn't have time. It's ironic I couldn't find time to talk about overloading.

Andrei

I was away for few days and then partially busy for several more days, I am sorry and I will try to get up to date.

Gary Whatmore:

> Guys, I made several sockpuppet reddit accounts to mod down the two guys criticising this thread.<

That's worse than desiring to add some examples of D code to Wikipedia, I was criticized about :-)

-------------------

One of the comments of the Reddit thread seems a bit interesting:

nullc:
>When I first read about D I was hoping that they'd limit overloads to pure functions, a substantial decrease in the maximum riskyness/surprise-factor of an overload hidden operation.<

Is requiring the Operator Overloading member functions to be pure a good idea?

Bye,
bearophile

On Sunday 12 December 2010 23:20:36 bearophile wrote:
> I was away for few days and then partially busy for several more days, I am sorry and I will try to get up to date.
> 
> Gary Whatmore:
> > Guys, I made several sockpuppet reddit accounts to mod down the two guys criticising this thread.<
> 
> That's worse than desiring to add some examples of D code to Wikipedia, I was criticized about :-)
> 
> -------------------
> 
> One of the comments of the Reddit thread seems a bit interesting:
> 
> nullc:
> >When I first read about D I was hoping that they'd limit overloads to pure functions, a substantial decrease in the maximum riskyness/surprise-factor of an overload hidden operation.<
> 
> Is requiring the Operator Overloading member functions to be pure a good idea?

Absolutely not. I don't see what that poster thought would be gained by enforcing that, but it's _really_ easy to have useful and legitimate overloaded operators which can't be pure. Purity has its uses, but I think that that poster is overestimating them if they think that requiring overloaded operators to be pure would be generally useful, let alone solve much in the way of problems.

- Jonathan M Davis