Re: Bug in Auto Functions and Template? Or Am I Just Crazy...

2012-06-28 Thread Michael
Good I know I spotted something _real_ this time! On Wednesday, 27 June 2012 at 11:55:11 UTC, Timon Gehr wrote: On 06/27/2012 01:24 PM, Timon Gehr wrote: On 06/27/2012 11:07 AM, Michael wrote: Hello all, I came across some weird behaviors yesterday and I can't figure out what it's about.

Re: Concurrency in D

2012-06-28 Thread Minas Mina
On Wednesday, 27 June 2012 at 23:50:17 UTC, Ali Çehreli wrote: On 06/27/2012 04:05 PM, Adam Burton wrote: For example I would like to have a thread calculate the sum of the first half of an array while another thread would calculate the other half, and I could add the two results at the

Re: Concurrency in D

2012-06-28 Thread maarten van damme
yeah, I didn't knew std.parallelism was so easy to use. Speed up was really big for minimal effort.

Re: aa.remove in a destructor

2012-06-28 Thread Ellery Newcomer
On 06/26/2012 12:41 PM, Steven Schveighoffer wrote: I want to red flag this code for another reason. You must *never* access GC-allocated references in a destructor, to do so will make the program crash randomly. The docs should be so assertive (not that I read them or anything). The

Waiting for Godot

2012-06-28 Thread Pragma Tix
Am 27.06.2012 14:25, schrieb Steven Schveighoffer: On Wed, 27 Jun 2012 05:37:00 -0400, Minas Mina minas_mina1...@hotmail.co.uk wrote: How can I do that? Why not list.remove(x); like in STL? SList is quite unusable. If you are looking for STL-like containers, there is dcollections which has

Re: implicit conversion to alias this

2012-06-28 Thread BLM768
I'm fine that the assignment to C is verboten. I'd disallow the  first assignments to and would like to know, why they are kept. OK, now I get it. I'm not sure why they're allowed, either; I guess that it's just because it's written with assignment syntax. On second thought, it might be

Re: implicit conversion to alias this

2012-06-28 Thread Jonathan M Davis
On Monday, June 25, 2012 22:06:20 Tobias Pankrath wrote: - struct A { bool a; alias a this; } struct B { int b; alias b this; } A a = false; // works B b = 12; // works struct C { A aa; B ab; } C c = { false, 12 }; // does not work, because the implicit conversion does

Re: implicit conversion to alias this

2012-06-28 Thread BLM768
I'm fine that the assignment to C is verboten. I'd disallow the  first assignments to and would like to know, why they are kept. OK, now I get it. I'm not sure why they're allowed, either; I guess that it's just because it's written with assignment syntax. On second thought, it might be