Re: looking for V[string] workarounds

2013-03-20 Thread Dan
On Wednesday, 20 March 2013 at 17:44:16 UTC, Ali Çehreli wrote: In that case, brute force to the rescue (nc stands for non-const): :) this(const(Series[string]) source) { auto nc_source = cast(Series[string])source; itemToSeries = nc_source.dup; } Wow - that worked. Thanks! I h

Re: looking for V[string] workarounds

2013-03-20 Thread Ali Çehreli
On 03/20/2013 10:24 AM, Dan wrote: On Wednesday, 20 March 2013 at 17:11:02 UTC, Ali Çehreli wrote: The code compiles with 2.062 and an earlier version of 2.063 if you accept letting go of const-correctness there: this(Series[string] source) { Thanks Ali. But, removing const there then requir

Re: looking for V[string] workarounds

2013-03-20 Thread Dan
On Wednesday, 20 March 2013 at 17:11:02 UTC, Ali Çehreli wrote: The code compiles with 2.062 and an earlier version of 2.063 if you accept letting go of const-correctness there: this(Series[string] source) { Thanks Ali. But, removing const there then requires non-const instances to be p

Re: looking for V[string] workarounds

2013-03-20 Thread Ali Çehreli
On 03/20/2013 07:34 AM, Dan wrote: Can the following be made to build and run, but keep the intent of what is shown. I realize it touches on several bugs related to const, postblit, and map - but I'm having trouble finding the magic combination. The idea is simply have assets store multiple serie