Re: Status of AA's?

2013-03-29 Thread Dmitry Olshansky
29-Mar-2013 00:54, 1100110 пишет: On 03/28/2013 03:05 PM, Dmitry Olshansky wrote: The built-in ones are a minefield for anything more complex then a dictionary of string->int :) Please, last I checked, they were still a minefield for that... Random crashes, basic issues with the type system..

Re: Using inout in delegate

2013-03-29 Thread Kagamin
On Thursday, 28 March 2013 at 16:34:47 UTC, Maxim Fomin wrote: probably bypassing type system. try to bypass the type system; we just saw the variables are typechecked.

Re: Using inout in delegate

2013-03-29 Thread Maxim Fomin
On Friday, 29 March 2013 at 09:03:11 UTC, Kagamin wrote: On Thursday, 28 March 2013 at 16:34:47 UTC, Maxim Fomin wrote: probably bypassing type system. try to bypass the type system; we just saw the variables are typechecked. You saw one particular example, the problem is much bigger.

Re: Status of AA's?

2013-03-29 Thread Dicebot
Issues as described by H.S. Teoh are still available in wiki : http://wiki.dlang.org/AA_Implementation_Issues tl; dr: current implementation is so hacky, that proper transition is no small feat. I wanted to continue this project initially, but then decided there are other more important things

Re: Question about auto ref

2013-03-29 Thread Namespace
Ok I interpret this as a rejection of the idea.

Re: enum type changes according to context ?

2013-03-29 Thread Jonathan M Davis
On Thursday, March 28, 2013 16:02:18 Timothee Cour wrote: > In code below, does transTable have a well defined type? > it seems to change from line 9 (string[char]) > to line 10 (string[dchar])... > > rdmd -version=bad main //CT erro > rdmd main //works > > import std.string; > void main(){ >

Re: Question about auto ref

2013-03-29 Thread Martin Drasar
On 29.3.2013 11:59, Namespace wrote: > Ok I interpret this as a rejection of the idea. This seems like a language design decision and as such would get much broader audience (and probably more responses) in digitalmars.D than in learn forum. Threads in here can get overlooked easily. Maybe you sh

Re: Question about auto ref

2013-03-29 Thread Namespace
On Friday, 29 March 2013 at 12:57:55 UTC, Martin Drasar wrote: On 29.3.2013 11:59, Namespace wrote: Ok I interpret this as a rejection of the idea. This seems like a language design decision and as such would get much broader audience (and probably more responses) in digitalmars.D than in l

alias this + std.array.popFront

2013-03-29 Thread Tobias Pankrath
Hello, the following struct is not an input range because you can't call popFront on it, however I'd say you should be able to. struct Wrapper { int[] _data; alias _data this; } Bug or intended behaviour? Thank you!

Re: alias this + std.array.popFront

2013-03-29 Thread Tobias Pankrath
On Friday, 29 March 2013 at 22:13:31 UTC, Tobias Pankrath wrote: Hello, the following struct is not an input range because you can't call popFront on it, however I'd say you should be able to. struct Wrapper { int[] _data; alias _data this; } Bug or intended behaviour? Thank you!

Re: alias this + std.array.popFront

2013-03-29 Thread Jonathan M Davis
On Friday, March 29, 2013 23:22:36 Tobias Pankrath wrote: > On Friday, 29 March 2013 at 22:13:31 UTC, Tobias Pankrath wrote: > > Hello, > > > > the following struct is not an input range because you can't > > call popFront on it, however I'd say you should be able to. > > > > struct Wrapper { > >

GtkD "No GSettings schemas installed"

2013-03-29 Thread Josh
This is the code causing the problem: class myInputDialog : Dialog ... this() { super("Please enter file location...", this, GtkDialogFlags.MODAL | GtkDialogFlags.DESTROY_WITH_PARENT, [StockID.OK], [GtkResponseType.OK]); with (addButton(StockID.OPEN, GtkResponseType.NONE)) {

how to define opCast outside class

2013-03-29 Thread Timothee Cour
version(good) works. version(bad) does not. Can we make std.conv.to work for out-of-class opCast? Use case: same reason as UFCS, where we don't wanna define all methods inside class def, leading to possible extensions later. Currently this IS a problem when class A is in a library over which we hav